Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
SimTX Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
NTFZh
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Message Structure & Format Examples == All branches of the Russian Armed Forces use standardized formats for voice and Morse code radio messages. Depending on the traffic type, messages follow structured preambles and specific tactical formats (such as Monolit or Uzor). === 1. Standard Preamble & Urgency Levels === Non-ordinary messages are typically preceded by an urgency level identifier (*Samolet*, *Raketa*, *Vozdukh*, or *Monolit*) and a strict preamble structure: * '''Preamble Components:''' Serial number -> Group count -> Day of the month -> Moscow time -> Serial number confirmation. * '''Routing Prefixes:''' Origin callsigns are preceded by ''ot'' (voice) / ''FM'' (Morse), and destination callsigns by ''dlya'' (voice) / ''FOR'' (Morse). If the field following ''DLYA'' is left blank, it indicates a broadcast message intended for all stations on the network (or currently uncertain). === 2. Monolit Format Specification === Monolit messages take the following strict format: * '''Structure:''' [Recipient Callsign] + [5-digit group] + [Code word] + [Two 4-digit groups] ... * '''5-digit group:''' Connected to the recipient(s), configured either as a single recipient followed by a single/multiple 5-digit groups, or multiple recipients followed by an equivalent amount of 5-digit groups. * '''Content:''' The code word usually addresses an envelope with instructions, with the accompanying pairs of 4-digit groups forming the core message to be decoded using that given envelope. * '''Zone-covering messages (Зоны):''' Messages using this exact Monolit format but carrying no actual operational meaning (often logged as background or dummy traffic). === 3. Recorded Examples of All Observed Message Types === * '''Standard Monolit Voice Messages:''' ** ''05/08/2026 (4774 kHz):'' *** Cyrillic: `НТФЖ 52156 НАТИЖ 0100 4638` *** Latin: `NTFZh 52156 NATIZh 0100 4638` *** Structure Analysis: Station ID (*НТФЖ*), recipient callsign/5-digit group pairing (*52156*), followed by the recipient/code section (*НАТИЖ*) and operational groups (*0100 4638*). ** ''22/08/2026 (4844 kHz):'' *** Cyrillic: `НТФЖ ТОД3 86106 БИМБАЛОКЗ 0870 3256 Приём` *** Latin: `NTFZh TOD3 86106 BIMBALOKZ 0870 3256 Priyom` *** Structure Analysis: Monolit format starting with station ID, recipient callsign (*ТОД3*), connected 5-digit group (*86106*), code word (*БИМБАЛОКЗ*), and two coordinate/content 4-digit groups (*0870 3256*). ** ''07/09/2026 (4844 kHz):'' *** Cyrillic: `НТФЖ 54805 ПОВКЛАМА 8075 9089` *** Latin: `NTFZh 54805 POVKLAMA 8075 9089` *** Structure Analysis: Slow operator voice Monolit delivery with minor execution errors, followed by an open-mic room acknowledgment leak. * '''Special / Anomalous Voice Message:''' ** ''16/08/2026 (4774 kHz):'' *** Cyrillic: `НТФЖ 50261 4774 КТШЦ 5206 0824` *(Note: contained internal timestamp/date contradictions)* *** Latin: `NTFZh 50261 4774 KTShTs 5206 0824` *** Structure Analysis: Station ID (*NTFZh*), unit/recipient pairing (*50261*), frequency reference (*4774*), code word (*KTShTs*), and anomalous parameter groups (*5206 0824*). ** ''07/09/2026 Sign-off Broadcast (4844 kHz):'' *** Cyrillic: `Я НТФЖ, сообщение для всех станций мониторинга: передатчик отключается менее чем через минуту, повторяю, передатчик отключается менее чем через минуту, завершаем сегодняшние передачи. Прием.` *** Translation: Explicit closing announcement notifying monitoring stations of an imminent transmission shutdown. * '''Voice Test Counts (Proverka Mikrofona):''' ** ''04/08/2026 & 22/08/2026 (4774 / 4844 kHz):'' *** Cyrillic: `НТФЖ 1 2 3 4 5 6 7 8 9 10 Проверка Микрофона Приём` *** Translation: Station ID — Numerical test sequence (1 to 10) — Microphone Check — Over. ** ''02/09/2026 (4844 kHz):'' *** Cyrillic: `НТФЖ 1 2 3 4 5 6 7 8 9 10 0 Проверка Микрофона Приём` *** Translation: Station ID — Extended numerical sequence (1 to 10, ending in 0) — Microphone Check — Over. ** ''07/09/2026 (12005 kHz):'' *** Cyrillic: `Prymka61, проверка микрофона, 1 2 3 4 5 6 7 8 9 10, Как слышно? Свяжись со мной по телефону. Прием.` *** Translation: Callsign Prymka61 — Microphone check — Numerical sequence (1 to 10) — How do you copy? Contact me by phone — Over. * '''Morse / DLYA Telegraphy & CW Messages:''' ** ''22/08/2026 (4844 kHz):'' *** Cyrillic / Morse text: `XXX XXX DLYA DE NTFV == 54987 MOMBALKH MONTU MOBUTU KONTO AORIS == 5640 8975 K` *** Latin transcription: `XXX XXX DLYA DE NTFV == 54987 MOMBALKH MONTU MOBUTU KONTO AORIS == 5640 8975 K` *** Structure Analysis: Attention signal (*XXX XXX*), blank destination field following *DLYA* indicating a general broadcast to all stations (or uncertain recipient), origin separator (*DE*), variant callsign (*NTFV*), separated by double signs containing encrypted code groups, closing parameters, and invitation to transmit (*K*). ** ''07/09/2026 (4862 kHz CW):'' *** Morse text: `XXX XXX NTFV 54805 POVKLAMA 8075 9089 K TTT TTT` *** Structure Analysis: Parallel Morse dispatch matching the voice Monolit message broadcasted simultaneously on 4844 kHz. * '''Digital Modes & Telemetry Transmissions:''' ** ''RDFT & RTTY Encrypted Data:'' Automated teleprinter bursts logged during scheduled broadcast windows (e.g., 24/08/2026 on 4844 kHz). ** ''CIS-12 (T-230) Encrypted Traffic:'' High-grade multi-tone tactical digital data streams observed following the Nizhny Novgorod relocation (e.g., 01/09/2026), dual-frequency deployments (4844 & 12005 kHz on 06–07/09/2026), and used dynamically as anti-pirate self-defense jamming on 07/09/2026. ** ''CIS-20 Encrypted Traffic:'' Complex digital data packets deployed during unstable propagation and hardware tuning tests (e.g., recorded on 02/09/2026).
Summary:
Please note that all contributions to SimTX Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
SimTX Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)