Seventy-second edition of the N&O column / Spooks newsletter

(Date: Mon, 03 May 2004 22:40:41 +0200)

Voice stations | Morse stations | Various modes
Intelligence profile : Armenia | Unid stations | Military stations | Logs
Index | NS NL Home

Military stations

CIS navy Morse communications

Compiled by Fritz

We received a number of updates to last month's article. Enough for Fritz to rewrite it.


1 Introduction
  A very short look back 30 years
Standard Morse messages format
2 Main branches of the CIS Navy
  Moscow Headquarters
The Northern Fleet
The Baltic Fleet
The Black Sea Fleet
The Pacific Fleet
The Caspian Flotilla
The Mediterranean Eskadra
The Naval Air Force
  Frequencies, call signs and message formats
4 Northern Fleet HQ Severomorsk RIT
  Baltic Fleet HQ Kaliningrad RMP
Black Sea Fleet HQ Sevastopol RCV
Pacific Fleet HQ Vladivostok RJS
Frequencies, call signs and message formats
5 Naval Air Force AV-MF (Aviatsiya Voyenno-Morskoyo Flota)
  Frequencies, call signs and message formats
6 The station RDL

1. Introduction

Nowadays there still is much Morse traffic to listen to. And the Navy must have good reasons to do so - even aboard of aircraft. Morse CW is cheap and straightforward; many examples suggest, it often is used as last attempt in case of technical - or propagational problems with fast transmission modes. It is however absolutely clear: the vast amount of data is exchanged by transmission lines via satellite or landline, the keen CW listener is feed off with a few crumbs, don't expect to catch RIW daily on 11000!

Much of the following informations may be outdated, incomplete or even wrong. Please forgive me! I did browse my own loggings, many Navy Websites (with inconsistent contents), some WUN/N&O Newsletters, the archive CD of Klingenfuss Publications, Trond's Website and tried to make the best out of it.

Thanks go to Tom DL8AAM, Ary and several correspondents who wish to remain anonymous, who came up with many useful remarks for the draft of this little work. If you do have additions, corrections, amendments - and there is no doubt, many do - please let the Editor know, thanks.


Around 30 years ago monitoring the Soviet Navy Morse communications was very rewarding. Every flotilla had its individual "style". Comparing preambles, call signs or just some habits of the operators frequently allowed listeners to assign the messages unambiguously to a fleet and/or vessel.

Especially the Black Sea Fleet was easy to trace from Europe when they sailed Odessa. Much has changed since complicating the life of the inclined eavesdropper. Maybe one of the reasons of the modernization was the disastrous Warsaw Pact adventure in the former CSSR 1968.

Serious supply gaps, due to comms problems, forced operators to order provisions even in plain Russian.

Years later WAPA came up with a common format of messages for all forces. It is well known and still in use at all tactical and point-to-point CIS networks:

162 30 18 1202 162 = 517 = ppppp 5ALG or 5FGx28 azkbz = 667 +
  (or 11111)   (or 18028)


The preamble may include the senders callsign too. If the message is preceded by the (senders callsign) QTC the message is sent blind or broadcast (to a CQ callsign).

162 message number
30 group count
18 day of month
1202 local time
517 appointment code, a specific person or dept at the addressee


Accentuated letters used in the text are:

MorseCode spoken
ae .-.- ja
oe ---. ch
ue ..-- ju
ch ---- sh

The code of the final group is usually as follows and does not contain accentuated letters:

1 2 3 4 5 6 7 8 9 0
a b w g d e v z i k


Another alternative with accentuated letters is this set:

1 2 3 4 5 6 7 8 9 0
ae w e r t y u i o p

CIS Navy stations do use this format or variants, e.g. the last group is not coded, group count may differ by 1, etc. The same preamble is used for Meteo bulletins and Nautical Warnings, which in turn, may originate from merchant shipping. As we do not know, to a large extent, the meaning of the call signs, it is not even possible to separate RUS and UKR stations positively.

Without professional DF-Systems, (my Grahn Loop definitely is not good enough) we often cannot assign stations to a geographical region. Even worse: Tactical networks in Russia and Ukraine normally change call signs daily (maybe every ten days). And be careful, when trying to distinguish stations on the base of the local time group: this is the message preparation time, which may differ by hours from the local transmission time. Navy Nautical Warnings often have been issued the day before. Using "CIS" instead of RUS, BLR or UKR keeps me on the safe side. One of our correspondents is perfectly right however with his remark that tactical nets messages are less delayed than naval traffic. You wouldn't see "old" messages in their networks.

2. Main branches of the CIS navy

Should one include any numbers of ships, aircraft, etc here? They must be wrong, I knew in advance. Which are correct figures? The following numbers come from sources on the net. I received (thanks a lot) however reactions, saying, that "all the numbers .... are GREATLY exaggerated in all of the fleets". Cutting the number by 2/3 should be ok. The Pacific Fleet for example only has around 15 submarines and "less than 30 combatants of corvette size and up".

HQ Moscow Call sign RIW


Northern Fleet
HQ Severomorsk Call sign RIT
    a major repair/construction and trials base
  Naval Bases in Gremikha, mostly abandoned
    Ura Guba
    Litsa Gulf
  Home ports for 37 nuclear submarines
    22 other submarines
    47 principal surface combatants
    10 coastal and small ships
  Naval Aviation 20 Su-39 fixed-wing aircraft
    10 antisubmarine warfare helicopters
  Shore based aviation 200 combat aircraft
    64 helicopters
  Ground Forces 2 naval infantry brigades
    1 coastal defense regiment
    1 air defense missile regiment


Baltic Fleet
HQ Kaliningrad Call sign RMP
  Naval Bases in Baltiysk
  Home ports for 9 submarines
    32 principal surface combatants
    100 other surface vessels
  Naval Aviation 112 combat aircraft
  Ground Forces 1 naval infantry brigade
    coastal rocket unit


Black Sea Fleet
HQ Sevastopol UKR Call sign RCV
  Naval Bases in Odessa UKR
    Ochakov UKR
    Chernomorskoe UKR
    Novoozernii UKR
    Feodosiya UKR
  Naval Base near Novorossiisk RUS
  Home ports for 44 (*) surface combatant
    80 (*) auxiliary vessels


(*) Russian and Ukrainian sources state quite different figures.

After the desintegration of the former Soviet Union 1989 a series of agreements arranged the Black Sea Fleets partition between Russia and Ukraine.

Pacific Fleet
HQ Vladivostok Call sign RJS
  Naval Bases in Petropavlovsk-Kamchatskiy
    Magadan, almost completely abandoned by the Navy
    Sovetskaya Gavan, greatly abandoned
  Home ports for 50 nuclear submarines
    25 non-nuclear submarines
    65 major combatants
  Shore based Aviation 250 combat aircraft and helicopters
    2 Bomber regiments
  Ground Forces 1 Naval Infantry Division, later reorganised into brigades


Caspian Flotilla
HQ Astrakhan Call Sign unknown, if any
  Naval Base in Aktau KAZ
  planned in Fort Shevchenko RUS and in Aral RUS
  Home ports for 2 frigates
    12 patrol boats
    50 other small vessels


The Caspian Flotilla is a small fleet for coastal defence and waterways patrol. Command and equipment are shared with Azerbaijan and Kazakstan.

Mediterranean Eskadra
HQ Tartus SYR Call sign unknown, if any
  Naval Forces  
    1 aircraft carrier
    1 destroyer
    1 frigate
    1 tanker
    some nuclear submarines with SLBMs


The Warsaw Pact ceased to exist in 1991 and the powerful Soviet Mediterranean Eskadra withdrew from the Mediterranean. In 1996 battle ships, guided missiles cruisers and some auxiliary ships of the Russian Navy for the first time again deployed in the Mediterranean to show flag. Since then Russian Navy ships came back to monitor the crisis in former Yugoslavia and for bilateral operations with the US Navy.

Our expert commentator makes the additon however, that today the "Med Eskadra is defunct, and definitely has no carriers, destroyers or SSBNs with SLBMs on board". In Tartus "is always one ship" - sort of auxiliary. Not heavy Morse traffic to be expected thus, I guess.

Naval Air Force (Aviatsiya Voyenno - Morskoyo Flota AV-MF)

HQ Moscow Call sign RJF94 (*)


Black Sea Fleet Naval Aviation (VVS ChF)
HQ Sevastopol UKR Call sign RJC48 (*)
  Bases in Gvardeyskoye UKR
    Veseloye UKR
    Oktyabrskoye UKR


Baltic Fleet Naval Aviation (VVS SF)
HQ Kaliningrad Call sign RCB (*)
  Bases in Chkalovsk
    Bykhov BLR


Northern Fleet Naval Aviation (VVS NF)
HQ Murmansk Call sign RJC38 (*)
  Bases in Olenia
    Kuznetsov, (comment: aircraft carrier, not an airfield)


Pacific Fleet Naval Aviation (VVS PF)
HQ Vladivostok (?) Call sign RCH84 (*)
  Bases in Petropavlovsk
    Sovetskaya Gavan


(*) These call signs actually are in use. The allocations would make sense, but are absolutely not confirmed.

Another, quite trustwordio/nsnthy approach I found elsewhere:

RJF94 HQ Naval Air Transport
RJC48 Naval Air Transport Southern Sector
RCB Naval Air Transport Western Sector
RJC38 Naval Air Transport Northern Sector
RCH84 Naval Air Transport Eastern Sector


3. CIS navy headquarters Moscow call sign RIW

RIW is more or less regularly on the air. It listens on several frequencies and answers on 14556 11000 9145 in first instance. Two or all three frequencies may operate in parallel.

Many examples of traffic suggest, RIW prefers to use CW if propagation or technical problems do not allow the use of fast transmission modes. RIW operates very smart, keeps calling for a long time, reduces speed and even uses words in plain. If the station does not comply with regulations, RIW will tell him soon or even pretend not to understand, thus making the station repeating over and over again the text. The signal becoming weak or nil may mean RIW turns antennas and you may be nulled-out. Don't draw a line from Moscow to your QTH, making guesses: RIW is a function (HQ) and not a transmitter site. Smolensk is just one possibility. Khiva, a large military site and a preferred target for US eavesdropping from former Persia, is situated south of Lake Aral and often mentioned to use RIW. It is not a naval installation however.

As one of its main purposes, RIW allocates frequencies for further traffic, which in many cases is in voice. Two systems are known:

CIS Navy possibly uses one or several systems of

Examples of traffic with Navy HQ:

For MS-5 traffic RIW would use the following instructions

14556 15.8.03 1410z RFH70 de RIW QSA2 QSA? k (no answer)
    1425z RFH70 de RIW k (no answer)
    1437z RFH70 de RIW k
    1447z RFH70 de RIW QYT4 QWH 9700/9700 =
12056/12056 QSX 8440/8440 = 12414/12414 k
9700   1450z MS-5 tfc
14556   1500z RFH70 de RIW QYT4 QMO ok? k RIW QLS ok? k ......


CIS Forces use an extended set of Q-Codes. Some are known, many others not. Accented letters are not used. Recently I noted the use of "new" Z-Codes. They just replace Q with Z, e.g. ZTC = I have message for you. Doesn't make it easier for us...

QYT4 I will use MS-5 system
QWH 9700/rptd = 12056/rptd I will send on 9700, alternatively on 12056
QSX 8440/rptd = 12414/rptd I will listen on 8440, alternatively on 12414
QWH 9700/8536 = 12056/12572 Would mean: The link will run with two parallel frequencies.
Doesn't seem to be as popular as it was once.
QYT4 QMO Adjust your MS-5 system
QLS Use (upper) alternative frequency or Change frequency!


Luckily we can hear one of the CIS Forces xxx Flash Messages

14556 11.8.03 0730z uuu uuu uuu xxx xxx REO REO 89292 bogarnyj
731 00611 k



5383 16.11.03 1730z WLHN de RIW xxx xxx IA6N IA6N longbanit
2174 5893 k


Messages in the normal CIS format are sent from time to time

14556 30.12.99 0800z RDND de RIW QTC k
RIW 973 22 11 1105 973
= ppppp (5ALG) rpt al RIW k


If a station does not reply fast enough or has other problems, RIW will keep it waiting or will tell it.

10676 11.8.03 0850z RJK69 de RIW QYT4 QSX 9733/9733 = 11094/11094
QWH 12746/12746
= 14600/14600 ok? K
RIW de RJK69 QRS rpt k
RJK69 de RIW QCZ k
RJK69 de RIW QYT4 QSX 9733/9733
= 11094/11094
QWH 12746/12746 = 14600/14600 ok? K

Other possibilities might be:

Quite often RIW relays messages to others

14556 11.8.03 1400z RFE76 de RIW QTC 411 66 11 1607 411 = sml =
fm RMP = rrrrr (5ALG) RIW k


Another example of RIW traffic

14556 10.12.03 0930z RIW QSA? QTC k
RIW 21 22 10 1305 21 = 11111
(5FG) =
rpt al + RIW
RIW rpt corcol 5 17449 k
RIW c k
14556   0950z RAL68 de RIW QRC? K
RIW 416 121 9 0516 416
= fm RIT for RMLZ =

Did something go wrong?

14556 7.1.04 1606z RGV82 de RIW QSU1 QSX 8228 ok? k
8228     USB Voice Plain RUS
14566   1618z RGV82 de RIW QSU1 sk RIW k

This time again it lasted a long time to establish a MS-5 QSO.

14556 30.1.04 0915z RMZW de RIW QYT4 QSA4 QSA? k
      RIW QLS QYT4 QSX 12398 ok? k
      RIW QCM QYT4 QCM k
12398   0958z tfc MS-5

RIW ITU registrations amounts to 76 frequencies. The following may be worth to try.

14556//11000//9145 RIW exclusive, primary listening/answering
4956 10676
5128 10825
5383 12056
7580 12329
8523 12736
8536 12746
8678 12825
8788 12948
9523 13086
9573 13110
9700 14024
10176 14086
10388 14600


RIW has contacts to many stations, some of them are listed here. Most of the call signs I cannot assign. Namely the meaning of collective calls are of vital interest to get any further.

The RMxx calls are most probably Naval Vessels, but this is not the case for ALL RMxx calls: RMXV, RMEG, RMDZ, RMBB, RMLZ, RMUE.

R*** probably Naval Vessels: RBIZ, RCJG, RCRE, RDND.

Navy call signs, nowadays some warships appear to use this format too:
RAL46, RAL59, RAL68, RFE76, RFF78, RFH70, RFV99, RFX56, RGV82, RJH25, RJH57, RJK69, RJT22, RLA88.

4. The Northern fleet HQ (RIT)
Baltic fleet HQ (RMP)
Black sea fleet HQ (RCV)
Pacific fleet HQ (RJS)

Due to propagational reasons I wasn't lucky enough to copy RJS so far. RIT didn't appear often in my logbook recently. RMP and RCV clearly favour certain frequencies and their Weather Forecast - or Nautical Warnings Broadcasts can't be missed. They are sent in plain language and seem to correspond to those transmitted by Coastal Stations. The header used is the normal preamble. RCV is nearly daily on 5775 around 1600z. We may assume, that the call signs RKZ and REO used for Fleet Broadcasts are collective calls. Knowing collective calls used by RJS would help us much. Sometimes HQs maintain contact with other stations. Traffic may be Duplex - or Simplex Mode. Messages are 5FG or 5ALG with or without encryption group and coded end-group. Coincidence or not: I never copied these HQs with an xxx-message.

Some examples of traffic follow:

5224 12.2.03 0440z RGX94 de RCV QTC 726 40 12 0450 726 = nawip = txt
      is Naut. Warnings +


4079 12.2.03 2050z RKZ de RMP QTC 104 23 12 2222 104 = fm RJD69 = 22222 5FG(x21) 12021 + RJD69
      a special call sign, very often used


6873 24.11.03 1533z RJD69 de RMP QYT4 QSX 5456 k


3181 30.12.99 2037z ZRK7 de RMP QTC 281 22 12 0012 281 = fm RJD69 = 5FG(x23) k


11155 13.4.03 1421z ROK81 de RIT QTC 607 27 1754 607 =
      sml = 4FG = + RIT k
      ok k
      ok QRU k


11155 4.3.04 1515z RKW95 de RIT QSA1 QSA? k
      RIT QRV k (receives msg number 809)
      RIT QSL 809 k r k


11155 6.3.04 1420z same as 4.3., daily routine messages?


6873 14.7.03 1530z RMAE de RMP QSX 4948 QWH 3685 k
5916 9.12.03 1540z RKZ de RCV QTC 179 114 9 1600 179 = prognoz pogody ot 1800 9 do 1800 10 dehabrä ...
      (Meteorological Bulletin)


6873 8.2.04 1550z REO de RMP QTC 671 41 8 1815 671 = sml =
baltijskoe more opoweqenie nr 490
  (   Nautical Warning)


4055 13.2.04 1645z RIC87 de RCV QTC 168 37 13 1600 168 = nawip =
      031 256 karta 35120 ukraina .....
      (Nautical Warning)


N&O Newsletter Nr.70 received this logging:

7632 ?? 0030z RJS QSL QRR3 vvv vvv
    later RGK39 de RJS QSA? k
    0600z QSO RJS with RMAZ and RJQ60


Some current frequencies:

RIT : 5343, 6934, 7467, 11155 kHz
RMP : 3181, 4079, 5213, 5881, 6873 kHz
RCV : 4055, 4885, 5224, 5775, 5916 kHz
RJS : 3594, 10203, 13636, 13907 kHz


RIT recently had QSO with: RLA88, ROK81, RKZ, RJI64, RMLZ, RFE76, RJD80, RKW95
RMP recently had QSO with: REO, RIW, RJD69, RKZ, RUD76, RMAE, RGS57, RKF80, RJI64, ROK81, RFF79, RGV82, LFJ1, ZRK7
RCV recently had QSO with: RCJE, RHC84, RKZ, RGX94, RBE86, RMBB, RIP90, RIC87


Other call signs beginning with R*****

There are MANY other call signs of which it is not clear, whether they really are Navy calls. Many can be heard having QSOs, others are somewhere listed, but never have been copied. Here follow a few examples:

3LG call signs
RAC: Navy Collective Call of RJS?
RAM, RIF, RKS, ROT: Moscow Navy
RCN: Stepnyak Unid
RFA: Astrakhan Unid. Coastal station?
RIB: Moscow Unid
RJV: Tiksi Navy
RKL, ROD: Murmansk Navy
RMG: Saratov Navy
RMT: Chelyuskin Navy Antarctica
ROR: Nizhniy Novgorod Navy. N.N. was Gorki
RUA: Petrozavodsk Unid. Coastal station?
RUF: Sevastopol Unid. Coastal station?
RUT: Unid Navy
RUH: Unid Unid


4LFG call signs (I think not all are Navy)
RAL2, RFH2, RDU2 : Interesting ones, sometimes hopping around on many frequencies. NCS is RAL2 asking "QSA" and, if satisfied, tells next frequency. Testing frequencies?
REK4 : Unid
RFP8 : Povorothny
RFR6 : Pioner Sovkhoz
RKA2 : Unid
RHW2 : Unid
RLO2 : Unid
RMW2 : Unid


5LFG call signs (May be Mil, Meteo, TS, Intel, Mil Navy)
RAL46, RAL59, RAL68 : Navy
RFF78, RFF79 : Navy
RGX94, RGX96 : Navy
RJD80, RJD85, RJD99 : Navy
RMW32, RMW33, RMW36 : Navy


One of the comments that I got: "...not all Rxx## calls are vessels and not all are Navy.... They pick and choose. Shore stations use Rxx## calls too".

5. Naval air force AV-MF

Please remember the reservation made in 2. concerning call sign allocations and the correct designation of these forces.

8816 kHz is allocated to Aeronautical Mobile Services for the following Regional And Domestic Air Routes Areas:

4A North West Africa
6G China
12C Mexico
13J Brasil
14A South of Australia


8816 is regularly, but obviously illegally, used by CIS Naval Air Forces. Consequently their Four-Letter Location Indicators are for "internal" use. XLLS, XMKK, etc apparently are used because ICAO did not assign the X*** series. ULOL Velikiye Luki, a town about 400 km West of Moscow, is often served and does belong to the Russian Federation Series UL** of Location Indicators. UMWS most probably is an airport in Kaliningrad or Belarus, but not officially listed.

Let's have a look at the following example. Aircraft 26855 reports his flight from location XMKK to location XMKK. On its way it passes UMWS and ULOL and will, later in the evening, return to XMKK. Reports are made to the Regional Air Traffic Control RCB and to the HQ RJF94. Both stations do repeat the whole message until acknowledgement by the mobile.

1535z RJF94 RCB de 26855 QSA? QTC k
  26855 de RJF94 QRV k
  26855 de RCB QRV k
  26855 QTO QTR 1525 QRD XLLS XMKK QRE UMWS 1625 QAH 5700 k
  (RJF94 repeats message) k
  26855 ok k
  (RCB repeats message) k
  26855 ok k
1624z RJF94 RCB de 26855 QTC k
  26855 de RJF94 QRV k
  26855 de RCB QRV k
  26855 QQL UMWS 1622 QRE ULOL 1720 QAH 5700 QBD 0330 k
  (message repeated and acknowledged)
1715z RJF94 RCB de 26855 QTC k
  26855 de RJF94 QRV k
  26855 de RCB QRV k
  16855 QQL ULOL 1710 QAL XLLS 1805 QAH 5400 QBD 0300 k
  (message repeated and acknowledged)
1800z RJF94 RCB de 26855 QTC k
  26855 de RJF94 QRV k
  26855 de RCB QRV k
  26855 QQM XLLS 1806 k
  (message repeated and acknowledged)
2005z RJF94 RCB de 26855 QTC k
  26855 de RJF94 QRV k
  26855 de RCB QRV k
  26855 QTO 1950 QRD XMKK XLLS QRE ULOL 2100 QAH 5400 k
  (message repeated and acknowledged)


Official Q-Code series as well as CIS Codes are used:

QTC I have message for you.
QRV I am ready.
QTO I am airborne or I started at ... (hours).
QTR The time is ... (UTC used).
QRD I am bound for ... from ... .
QRE Estimated time of arrival at/over ... (place)is ... (time).
QAH Flight level/altitude is ... (in meters or barometric pressure in a standard atmosphere)
QQL I have passed ... (place) at ... (time).
QBD Fuel endurance is ... (hours and minutes).
QAL I estimate to land in ... (place) at ... (time).
QQM I will land in ... (place) at ... (time).


The following contacts have been logged:

Aircrafts 26858, 26855, 26896, 26869, 52880 had QSOs with the ATCs and HQ. RJF94 had QSOs with the ATCs. The ATCs had QSOs among themselves. Only RJC48 once contacted a "foreign" station: RDG90.

6. The station RDL

Listening to the CIS Forces communications without copying sooner or later RDL is rather unlikely. Officially it is listed as CIS Military HQ Moscow and many transmitting sites like Molodechno, Smolensk, Arkhangelsk, Krasnodar, Tashkent or Nizny Novgorod show up. A reasonable conclusion suggests RDL does form part of a VLF network together with RLO (St. Petersburg) and RKS (Moscow), both belonging to the CIS Navy. I believe RDL has to do with the CIS Navy, but unfortunately don't have any information about RKS and RLO.

RDL officially is listed on 19 frequencies, probably not all the right ones for the inclined listener .... Try these (no guarantees here):
4031, 6902, 7008, 7657, 9182, 10535, 10490, 11139, 11468, 11470, 12740, 12832, 14300, 14656, 14664, 19257.5, 20096, 21284, 22864 kHz.

The most popular frequency however is 18.1. RDL is regularly on the air, traffic is on both in Morse CW and BEE/36-50 (a FSK synchronous bitstream system, starting with 36 Bd, then changing to 50 Bd)for Navy Broadcasts and maybe other military branches. If you attempt to copy RDL on 18.1 be careful: the French Station HWU on 18.3 may interfere. With a ferrite rod antenna HWU is nulled out (hopefully!). Never mind, if your receiver doesn't cover 18.1. Often enough other frequencies are in parallel, e.g. 12832 or 19257.5. Patience is required!

Some sample messages of RDL:

18.1 29.01.04 0945z uuu uuu RDL RDL RDL88732 32267 88732 32267 88732 32267 k
      A very common format, always two 5FG rptd. The "uuu uuu" bit indicates it is routine. It hasbeen suggested, these messages may be comparedwith the status messages of the G and NL Navy, just a sort of authentication, checking whether everything is ok.
18.1 29.01.04 0917z xxx xxx (then continues with 36-50)
      XXX sent in Morse indicates a flash message. I do have my doubts however - there are so manyof them. We may assume anyway, XXX should getattention for a message of high priority.(note; the XXX messages can be compared withthe USAF EAM's. There are many EAM's a day,therefore the number of XXX messages is not acriterion. -Ary-)
10535 16.03.03 1500z XXX RDL 54837 33099 bajdvarahi 4572 9942 k (x2)
uuu xxx 12746 51118 birüzomyj 8887 0840
birmanskir 0495 5997 k
22864 16.02.04 1009z XXX XXX RDL RDL 20699 werwica 5690 01 1357 1247 k
7657 18.02.04 1610z XXX XXX RDL RDL 25120 08122 oteoina 2928 4286 k


Listeners delight: many xxx msgs on RDL. What are they meant for? They seem to use a certain set of codewords, some of them show up again after years and on different nets. Example: "ESUP", you'll find it back into the 90ies. XXX is like snooker: thrilling to watch, but I have no idea about the rules.

I never copied RDL having contact with an individual call sign or using the usual CIS preamble.

RDL seems to be of great importance, understanding its habits would bring us ahead considerably.

Logs and info supplied by Fritz, Jim, Sergey, Maciej and John.

Freq. QSX Callsign / remarks
18.1   RDL; Russian Military VLF Site Krasnodar.
3263 3263 DVB4, A66J, 8UYB, SJJQ, IVZ7
3334   DCAL, TSTW, 2AKF
3348   MFDX, 8PNT, 9PYZ, NKDS, 8WS9, JKFA, T1QW, PPB3, A2P2, GOAS
3363   SQQJ, 1BOS: SJJQ
3538   TD2P, MICX, OO4P, FAMR, 76SG, 5UHP, MBQ1, TVJA
3899   ZX4M, D47G
3954   QE6S, 9XDU
4021   1TDU, ATPE, 6GNJ, MHYR
4051   AI1R, FS1P
4379   REA4: AFHQ Moscow //5157 kHz
4446   RDL
4447   3LTT, 6NTL, C13N, CS4U, 5GOF, YFAK, TBTG, 4E7K, BRBS
4503 4503 B9Y9, NKT6
4898   ZM1E, PNTP
5157   REA4: AF HQs Moscow //4379 kHz
5407   8Q6T, BCIP, ZS76, PV2A, XXTJ, 3LPK, 6I5X, NU1D
6329 6329 RHC93 wkg RIR2 with scrambled morse setup ZZV ZZD3 ZZD3 K. ZDS ZZT. LVVMMMLKLMVKLVLL ... IMRX DRUACU.
6339   ZRI1, NB2W, 5TOB
7003   RGT77 RGT77 = 3LG = 5ALG k
7041   DFYQ, BCTP, QHNV,4TS4, LJ6J, GO6V, X18H,
7050   LG5Q
7056   NN4W, 9HAZ, L44V, NIBS, MGIE, Y65I, 9AW9, WO4N, 5GXS, F6EF, 5GXS, 5ZOK, GIJ2, WKPT
7932   OLFA, WKGK
7964   3H2K, EGYE
13004   F5MQ, LEV1
13843   YTOS
14300   RDL: "UUU UUU RDL RDL 21288 91676 k"


- Sample messages:
- Unid

This unid station is possibly also a CIS military station (see also last month's unid VTI8).

"No trace of VTI8 bcsts at 55-05 and 25-35 minutes each hour today (5 April)" says Attu. "However, at 07-17 and 37-47 minutes each hour, callsign SFO3 was active on 3699 kHz."

See also Newsletter 73 for more about Russian/CIS military transmissions.
See also Newsletter 74 for more about SFO3.

Polish military

Freq. Callsign
2028 Centrum01
2705 UWAGA! UWAGA! Tu Warmia, Angora Tecza Izera Fala 8307.
(Air Defense, Malbork -unconfirmed-)
UWAGA! UWAGA! TU Hawana, Hawana. Exercise??? (Fighter Squadron in Poznan/Powidz region -unconfirmed-)
2448 Uwaga Tu Warmia", same tx as on 2705 kHz.
4146 unid Polish navy
7783 Polish military in Bosnia.


See also Newsletter 73.


Voice stations | Morse stations | Various modes
Intelligence profile : Armenia | Unid stations | Military stations | Logs
Index | NS NL Home