HFU HF Underground
Loggings => Utility => Topic started by: Josh on May 31, 2019, 1727 UTC
-
Overview of Russian Federation Naval HF Comms
The Russian Navy
"The Crew—One Family"
VMF - Voyenno Morskoy Flot Rossiyskoy Federatsii
Military Marine Fleet Russian Federation
==================
Surface Ships of the CIS Navy employ cw "41st Channel" via hf radio networks "Globus" (globe), "Equator" (self explanatory) or "Vympel" (Pennant)
Globe seems to be the top echelon command network while Equator may mean hemispherical comms regions, Vympel (Pennant) may mean comms between units under a specific flag/fleet command and their subordinates
For example;
KRASNAYA OKTOBER (a very sneaky ficticious ruskii submarine) transmits to Murmansk RIT over the Vympel network, RIT then passes the traffic to Moscow RIW via the Globus network.
Submarines of the CIS Navy employ superfast telegraph (SAD = Russian acronym for high speed cw?) via radio mode "Akula-Splav" (Akula = shark, Splav = Alloy) or "49th Channel" via hf radio networks "Globus" (Globe) or "Okean" (Ocean). "49th Channel" may be Akula mode specific rather than routing all digital mode traffic. To be precise, Akula isn't CW, it's phase coherent FSK and PSK in Akula II. Subs aren't the only units to deploy Akula.
Often, CW traffic passage is preceded by tuning procedures composed of a series of Vs and/or random dits and dashes.
All stations that are going to be heard in this net period will be tuning their systems to the net freq.
Radio checks take place after every day/night frequency change; 1800Z & 0600Z.
Sessions are closed with "ZNN ZNN sk sk" by the NCS.
As a general rule, expect QTC traffic on the hour, synoptic traffic at 0000/0300/0600 etc you get the idea
For example, right now 2222Z 13DEC19 there's the faintest of very fast CW on 12464, my guess 30wpm or better and way outta my league.
The terms "CIS Navy" (Commonwealth of Independant States Navy) and "RN" (Russian Navy) are used interchangeably.
The Easy Ones
CIS Navy CW qrgs
Fleetwide primary freqs
08345 (1800Z to 0600Z)
12464 (0600Z to 1800Z).
However there are many regional frequencies that are used, and are being more used than primaries these days
The 0600/1800 QSY is apparently a suggestion not a maxim so one can find traffic on either freq regardless of the current Moscow Time; 3 hours ahead of UTC
8348 is a primary Pacific fleet frequency which may propagate to the US, also try:
3594
4048
4190
5233
5411
5142
6240
6242
6989
7630
7632
9142
10203
10834
10834
13636
13907
18373
If you're located in the midwestern US you'd logically try to hear traffic to Navy HQ St. Petersburg RAA on 8120 evenings/nights, and perhaps traffic to Navy HQ Moscow RIW on 8345 (after 1800Z) or 12464 (after 0600Z) as these HQ are geographically closer to the monitoring station than say Murmansk (artic circle) RIT 5343, 7467, 11155 or especially Vladivostok (pacific coast of Russia) RJS on 4048, 5411, 7632, 10203, 13636, if you lived on the west coast US you'd logically try for the opposite as Vladivostok is much closer and only a salty okean (ocean) away from you.
This will become even more apparent and important as the sunspot numbers keep dropping and propagation fails to deliver. Fortunately we have remote sdrs we can log into to get our itch scratched. Who coulda thunk in 1989 that today, from any place in the world that has innernet connection, one could freely log onto an sdr located in Moscow and tune the hf spectrum at will, perhaps mere blocks from Kreml.
Duplex Circuits;
Many RN CW nets in use are duplex, ship transmits on one freq, shore transmits on another.
RIW Moscow sends to ships on 9145, 11000, 14556
RCV Sevastopol sends to ships on 15586 day and 7566 night, with weather reports also on 5915, in the past on 10543
So when you hear traffic on 7345 or 12464 look for the other side on the above freqs, but these are by no means all in use.
Behold!
http://www.udxf.nl/CISN-December-2015.pdf
Callsigns CW Stations:
======================
RCV Navy HQ Sevastopol
REA4 Airforce HQ Moscow
RIT Navy HQ Severomorsk North Fleet
RJS Navy HQ Vladivostok
RIW Navy HQ Moscow
RMP Navy HQ Kaliningrad
RMxx Warship Individual Callsign
Voice (U/LSB):
=========
Rezim-A: In Red/Clear Voice
Rezim-B: In Green/Encrypted Using Yakta
Vpiriom: Over to you
Priyom: Reception (do you copy)
As to Q Codes oft mentioned in RN cw comms:
========
QBE Closing
QCM Broken/Interrupted
QCM QYT6 MS5 Link is Broken
QDW I listen on XXX freq
QRD Q: Where are you going to?
QRD XXXX A: I am going to freq XXX
QRO (?) Increase power (shall I?)
QRP (?) Decrease Power (shall I?)
QRR CW Encrypted Groups Simplex
QRX Q: When will you call me?
QRX 2222Z A: I will call you at 2222Z
QSA? Q; Whats your Strength of (my) Signal?
QSA2 A: Strength Of Signal is 2
QSU1 USB voice
QTC? Q; How many messages do you have for me?
QTC3 A: you have 3 messages
QWH XXXX? Q; will you send on freq XXX?
QWH XXXX A: I will send on freq XXX
QYR 81Bd FSK
QYS SSB Voice Duplex
QYT4 OFDM 12 Channel psk data/encrypted voice, vessels
QYT6 QBE Close MS5 Link
QYT6 MS5 Link
QYT9 75 Bd 200 Hz, fixed stations
CIS Forces often use Z and Q codes with much the same meaning as NATO Z and Q codes with a few of their own device.
Q and Z codes used by NATO and CIS forces;
http://www.radiotelegraphy.net/qsignals.htm
http://www.radiotelegraphy.net/zsignals.htm
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Common Daily Traffic Nets
Day
11165
12464 (Primary)
11000
10543
Night
08345 Northern Fleet (Primary)
08348 Pacific Fleet (Primary)
HQ/Naval Radio Reception Center Stations
RAA St. Petersburg National Defence Control Center
RDL All Strategic Nuclear Commands
RIT Severomorsk
RIW Moscow
RCV Sevastopol
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - -
Headquarters/Naval Base Radio Reception Centers;
Frq: Calls :
RAA : 14587(Sx) 12692 (Sx) 10795
RCV : 19201 13971 (Sx) 10309 (Sx) 08139 08014 07763
(Sx) 05916 05776 05736 05224 05094 (Sx) 03797
RDL : 22864 16912 14664 10452 08136
RIW : 14556(Sx) 12056 (Sx) 10540 (Sx) 07665 07664
RMP : 21438 12692 (Sx) 06832 05881 05775 04079 007
RJS : 16112
RIT : 12753 11155 06877 05443
RCB : 08816 05808 06877 05443
(Sx) = Simplex
xxxxx = Frequency not known
Afloat/Airborne Units;
Frq: Calls :
08020 RJE65 RJP24 RIR99
07861 RAL2 RFH2 RDU2 RHW2 RBL71
07815 RMW32 RMW36 RMW46
07786 RAL65 RHY73 RBDE RMGB
06989 RAL2 RHQJ RGH2 RMW2 RBL66
06957 RMW46 RGR97 RGR98 RGR88 RGR82 RGR85 RGR92
06836 RGR89 RGR90 RGR91 RGR94 RMW46
05823 RAL2 RKA2 RLO2 RBL70
05770 RWI2 RGY2 RHK6
05018 RJE65 RJP24
03353 RJP54 RJP54 RMJA RMUW REL5 REL5
03337 RMGZ RJP54
===============================
Russian MX CW Beacon Clusters:
==============================
3334.9 L-Marker St.Petersburg
3593.9 S-Marker Arkhangelsk
3594.0 C-Marker Moscow
3658.0 V-Marker Khiva-Abad Turkmenistan
4042.0 P-Marker Kaliningrad
4325.8 R-Marker Izhevsk/Ustinov
5153.8 P-Marker Kaliningrad
5153.9 S-Marker Arkhangelsk
5154.0 C-Marker Moscow
7038.8 P-Marker Kaliningrad
7038.9 S-Marker Arkhangelsk
7039.0 C-Marker Moscow
8494.8 P-Marker Kaliningrad
8495.0 C-Marker Moscow
10307.2
10528.0
10871.8 P-Marker Kaliningrad
10871.9 S-Marker Arkhangelsk
10872.0 C-Marker Moscow
13527.8 P-Marker Kaliningrad
13527.9 S-Marker Arkhangelsk
13528.0 C-Marker Moscow
13528.2 F-Marker Vladivostok
16331.8 P-Marker Kaliningrad
16331.9 S-Marker Arkhangelsk
16332.0 C-Marker Moscow
20047.9 S-Marker Arkhangelsk
20048.0 C-Marker Moscow
Location:
============
C Moscow
F Vladivostok
L St.Petersburg
P Kaliningrad
R Ustinov
S Arkhangelsk
V Tashkent
CIS AF/Navy HF Comms
--------------------------------------
Voice Freqs: all USB
"Long Range Aviation" generally means Tu95 and Tu22 bombers of the respective service
03555.0
04040.0 Russian Pacific Fleet
04150.0
04625.0 ?
04642.0
04672.0 Vologda Control
05420.0
05568.0
05596.0 Vorkuta, Amderma, Il'men, Arkhangelsk, Pechora, Syvkar (Syktyvkar) & NaryanMar
05617.0 Long Range Aviation
05628.0 Long Range Aviation
05635.0 Long Range Aviation
05700.0 Military Transport Aviation (VTA) (Apr 2018)
05803.0
05827.0
05830.0
05833.0 Long Range Aviation
05851.0 Russian Naval Air
05932.0
06296.5 ?
06490.0
06685.0 Military Transport Aviation (VTA)(secondary)
06689.0 Long Range Aviation (Pacific area)
06749.0 Military Transport Aviation (VTA)
06757.0 Ukrainian Air Force
07741.0
08033.0 Long Range Aviation (Sep-Oct) Bears, Tu22, etc
08090.0 Long Range Aviation (Oct-Apr)
08131.0 Long Range Aviation (Nov-Feb)
08136.0
08160.0 Baltic Fleet?
08192.0 Russian Pacific Fleet
08237.0 Russian Mediterranean Flotilla
08252.0 poss Russian AF
08294.0 Russian Pacific Fleet
08297.0 Russian Pacific Fleet
08439.0 Russian Pacific Fleet
08441.0
08847.0 Military Transport Aviation (Dec 2013)
08459.0 Baltic Fleet?
08884.0 Long Range Aviation (Pacific area)
08909.0 Long Range Aviation (May-Sep)
08950.0 Murmansk Control#
08974.0
10984.0 Russian Black Sea Fleet
11190.0 Ukrainian Air Force
11193.0 Moscow Radio#
11198.0 Khabarovsk Radio#
11200.0 Long Range Aviation-winter freq #170
11223.0 Long Range Aviation reserve
11226.0
11354.0 Russian Naval Aviation
11350.0
11360.0 Military Transport Aviation -primary
11362.0 Military Transport Aviation
11370.0 Long Range Aviation TU-95s
11380.0
11390.0 Murmansk Control#
15024.0 Moscow Radio#
18030.0 Military Transport Aviation
# Russian military aircraft will occasionally use Moscow Radio & Murmansk Radio
? Not positively identified
-------------------------------
Russian Naval Air Transport Net
-------------------------------
Stations:
RJF94......Central Sector Station, Moscow (PRIBOJ)
RJC38......Northern Sector Station, Murmansk (NOVATOR)
RJC48......Southern Sector Station, Sevastopol (NORKA)
RCH84......Eastern Sector Station, Vladivostok (MONOLOG)
RCB........Western Sector Station, Kaliningrad (KRAKET)
Aircraft...Four figures assigned each aircraft (2319)
Ground stations maintain communication with each other on separate frequencies; communication between Moscow and Vladivostok is often heard (RJF94-RCH84)
Station C / S Codename QTH Description
MOSCOW RJF94 'PRIBOY' ATC Central District
VLADIVOSTOK RCH84 'MONOLOGUE' ATC Eastern District
Petropavlovsk-Kamchatskiy Base
Sovetskaya Gavan ' Base
KALININGRAD RCB 'KRAKET' ATC West Region
Chkalovsk Base
Nivenskoye Base
Bykhov Belarus Base
MURMANSK RJC38 'NOVATOR' ATC North Division
Olenia Base
Arkhangelsk Base
Severomorsk Base
Kipelovo Base
SEVASTOPOL RJC48 'MINK' Kacha ATC Southern District
Gvardeyskoye Base
Veseloye Base
Oktyabrskoye Base
Kulbakino Base
Coast Radio Stations:
=====================
04357 Ryga Radio
08293 Radio
08294 Ryga Radio
08297 Klaipeda Radio
08770 Radio
08773 Kaliningrad Radio
13086 Ryga Radio
13197 Odessa Radio
Meteo Stations:
===============
03690.0 Tashkent Meteo FAX
04318.0 Moscow Meteo FAX
04560.0 Irkutsk Meteo Baudot RKR74
05108.0 Moscow Meteo FAX
09348.0 Tashkent Meteo FAX RCH72
14983.0 Tashkent Meteo FAX RBV76
Commonly Heard Callsigns:
===============
ADJEK-06 Unknown
ARBAD Moscow CIV Aero
ARBAD-63 Unknown
AVRORA Unknown CIV Aero
BOREJ-96
C Moscow Navy Marker
CENTRE Unknown
COSMO Unknown
D Unknown/Obsolete
DAIHATJ-59 Unknown
F Vladivostok Navy Marker
GOY-2 Unknown
K Unknown/Obsolete
KRAKJET Unknown Airforce Operator
KRASJETJ-79 Unknown
L St.Petersburg Navy Marker
NAVATER Unknown Airforce Operator
O Unknown/Obsolete
P Kaliningrad Navy Marker
PAROS-XX Unknown
PIWON-24 Unknown
PLAVETS-41 Unknown Navy Operator
POBED-01 Unknown
PRAWA-82 Unknown Right ?
PRIBOY Unknown Airforce Operator
R Izhevsk/Ustinov Navy Marker
RADAN St.Petersburg CIV Aero
RAW-2
RBV-76 Tashkent Meteo
RCH-72 Tashkent Meteo
RCV Navy HQ Sevastopol
REA-4 Airforce HQ Moscow
REO Unknown
RHP-27
RIT Navy North Fleet HQ Severomorsk
RIW Navy HQ Moscow
RKR-74 Irkutsk Meteo
RMHW Warship Unknown
RMMA Warship Unknown
RMP Navy HQ Kaliningrad
ROMAN-XX Unknown
ROTOR-35 Unknown Navy Operator
S Arkhangelsk Navy Marker
SKORA Unknown CIV Aero
T Unknown/Obsolete
TRUAS Unknown CIV Aero
UDZ-27
URO Diplostation Tripolis?
UXW Diplostation London?
UVB-76
V Khiva-Abad Navy Marker
VORMET Unknown Airforce Operator
WQL Diplostation Unknown
Y Unknown/Obsolete
YAROK Kiev CIV Aero
ZAPAT-_9 Unknown
ZAVOD-24
CIS Naval callsign convention and generally follow ITU convention.
Most calls; ship, shore, or air, prefix with R.
Stations are assigned signs from the RAA-RMZ range and RJC ## - RJH ##
There are exceptions to callsigns, for example Magadan, RTS
Aircraft seem to have a random 3/4/5F call after the R regardless of their home base.
Afloat units do not have calls related to their fleet; for example, Northern Fleet units from Murmansk do not prefix their calls with RJD.
RDL is generally believed to be a collective address to "all nuclear strategic forces", in essence RDL = EAM
WLHN is generally believed to be a collective address to all units of the Armed Forces
Submarine units don't have known given calls ota on hf, as subs mostly use laser/satcomm buoys with, presumably, Akula as backup. That being said, Akula is also used for recon/int work by afloat units (AGI) so not every Akula sig's going to be a sub.
http://i56578-swl.blogspot.com/2015/07/cis-navy-shark-akula.html
http://jproc.ca/rrp/rrp2/boresight.html
Much traffic generated on CIS naval nets is comprised of position and local weather reporting, they seem to follow the reporting guidelines in this publication;
https://www.jcs.mil/Portals/36/Documents/Doctrine/pubs/jp3_59.pdf
CIS NAVY Meteo Callsigns
RJE73 = BLACK SEA FLOT METEO
RJH45 = MOSCOW NAVAL METEO
RJH74 = NORTHERN FLEET METEO
RJD38 = BALTIC FLOT METEO
RJE65 = BLACK SEA FLOT HQ, NOVOROSSIYSK
Hydrographic messages are normally sent every six hours – 0600z, 1200z, 1800z and 0000z.
With the above in mind, radio hobbyists can track certain CIS Naval assets from port to patrol area, AGI and subs excluded.
Commonly active CIS Naval Base freqs
08460 RMP Baltic Fleet HQ at Kaliningrad
03395.5 Sevastopol RCV (simplex)
04079 Kaliningrad RMP (duplex)
04376.5 White Sea area ships calling Severodvinsk (duplex)
04635 White Sea area ships calling Severodvinsk (duplex)
05411 Vladivostok RJS (duplex)
08120 Navy HQ St. Petersburg RAA (simplex)
08345 Ship night primary (duplex)
08348 Pacific Fleet ship primary (duplex)
09145 Moscow RIW (duplex)
11000 Moscow RIW (duplex)
11155 Severomorsk RIT (duplex)
12464 Ship day primary (duplex)
14556 Moscow RIW (duplex)
19201 Sevastopol RCV (weather/nav warnings)
White Sea:
4376.5
4095.5
Caspian Sea
3877.5 Simplex
Ship of electronic reconnaissance project (example 864/B Baltiysk 72DRK)
Russian AGI class of ships (remember the USS Pueblo?) do not send hf cw weather/position reports unlike other afloat units, I presume they have laser/satcoms as well as Akula just like the subs. As most USN task forces grow their own RN AGI tail and there seem to be continuous RN AGI haunting NATO and USN naval bases, their position is known to USN regardless if they send on hf, the NATO/USN radio traffic they intercept is likely sent by laser/satcom to RAA and Moscow. There may be more than one AGI tailing USN forces, or near Cape Kennedy when rocket launches are to take place as missile telemetry is a high priority target for AGI ships of any nation.
Also while RN forces use Cyrillic morse, they use a lot of Q and Z codes with the same meaning Q and Z codes have in the west.
Afloat units can bypass their respective HQ and contact Moscow directly. This may be due to propagation not favoring HQ or by command. Likewise, afloat and airborne units have freqs they guard that are a hotline from Moscow for flash messages, as well as their HQ freq. It's not uncommon for various HQ or even afloat/airborne units to relay comms from units that aren't organic to that command.
CIS Naval forces have some 600 known HF freqs in use, you can find a list at udxf or elsewhere but units are presumed to be frequency agile and can pop up anywhere.
CIS Naval messaging has a hierarchy like most other military message systems;
MNL “Monolith” Flash (XXX in RN cw)
VZD “Air” Immediate
RKT “Rocket” Priority
SML “Aircraft” Routine
CIS Naval cw is often part of RN digital bcasts for setup and takedown of links, typically BFSK T600 modems, with the cw being created by employing a single tone of the BFSK pair as the cw carrier. I presume the modem traffic from land units is along the lines of the NATO/USN BRASS S4285 and 50/75Bd FSK bcasts.
https://www.isode.com/whitepapers/brass-to-br1eta.html
Main Russian Naval radio centers / callsigns in Rossii and English
Globus (Global Network)
RIW / RJE56 / PROGRESS / KOMPASS
Moscow
This station gets input from all other HQ, while lower commands get input from their respective afloat units.
This is the seat of political command.
RAA / RJC66
St. Petersburg National Defence Control Center
Russian Naval C3 center, base component is RJC66
This is Russian Navy HQ. All lower HQ and afloat/airborne units send to this station as SOP but those stations can and do bypass HQ and send direct to Moscow when tasked or when unable to raise HQ or get a relay to HQ. Certain priority traffic (Akula reception, typically meaning a sub or AGI) is simultaneously sent on to RIW via all means available, cw, fsk, land line, etc. Submarine related traffic has highest priority in RN comms.
Okean (Ocean Network)
HQ Calls and locations
Severomorsk RIT
Kaliningrad RMP
Sevastopol RCV
Astrakhan RJD52
Vladivostok RJS
Northern Fleet (Siewiernyj Flot)
(Arctic regions, North Atlantic Ocean, North sea, Norwegian Sea, white Sea, Northern inland waterways)
Severomorsk RIT (+ RJH57) / Wolfram
Severodvinsk RJD99 Swetok, "Flower"
Iokanga RJD80 Jagernaja / Ostrovnoj / Gremikha / Murmansk / Svetlana
Polyarny RIR2 Priroda, "Nature"
Murmansk RJD56 FlĂger, "Vane"
The Northern Fleet has also been tasked with Arctic Joint Strategic Command. This arctic activity is going to increase greatly in the next decades as Russia is spending billions on revitalising/modernising old bases as well as building new ones. Increases in personnel are likewise taking place as Moscow stakes claim to vast natural resources and the military advantages of an arctic position. We might expect to see more NATO and US activity in this region to counter the perceived threat.
Baltic Fleet (Baltijskij Flot)
(Baltic Sea, North sea, English Channel, Inland waterways)
Kaliningrad RMP (+RJD71) / Westnik, "Herald", "Messenger"
St. Petersburg RJD85 / Skakun, "Race horse", "Jumper"
Baltiysk RJD69 / Iskatelx, "Seeker"
Black Sea Fleet
(Black Sea, Mediterranean Sea, Caspian Sea, Red Sea, inland waterways)
Sevastopol RCV / Gwozdika, "Cloves"
Novorossiysk RJE65 / Topolx, "White Poplar"
Caspian Flotilla (Caspianski Flot)
(Caspian Sea, inland waterways)
Astrakhan RJD52 / Zazor, "Clearance" or poss "Gap"
Pacific Fleet (Tihookeanskij Flot)
(North Pacific Ocean, South Pacific Oceans, Bering Sea, inland waterways)
Vladivostok RJS / Grejder "Grader"
Vladivostok RJC60 / Ăśrist "Lawyer (Jurist)"
Strelok aka Pavlovsk Bay RJD97 / Ă–jnara "Sycamore"
Petropavlomsk Kamchatskiy RCC / Dekanat "Deanery (Deans office)"
Sowgwanx/Sovjetskaya Gavan RJD93 / Flejta "Flute"
Indian Ocean
(Indian Ocean, South Atlantic Ocean, inland waterways)
Bishkek RJH25 / Sibirak "Siberian"
Other RN bases such as training, hydrographic, testing;
Khabarovsk (Vladimirovka)
RAB99 / Gerkules (h is pronounced g in Rossii)
Moscow (MANIKINO)
RJE56 / SOKOL-2
Kyrgyzstan
RJH25 / KAKTUS
TX/RX site
Krasnodar (MARTANSKAYA)
RJH63 / GERAKL
Comms center/time signal authority
Chaldovar, KZ (Karabalta)
RJH66 / Marevo
Comms center/time signal authority
Vileyka, BLR
RJH69 / ANTEY
Comms center/time signal authority
Arkhangelsk (VOZHDORMA)
RJH77 / ATLANT
Comms center/time signal authority
Nizhniy Novgorod
RJH90
Comms center/time signal authority
Druzhniy
RJH99
Comms center/time signal authority
RIQ88 is an unid land station in control of a transport aircraft network.
8816 seems to be their primary ops channel with 7932 as backup/emergency, monitored traffic is often in contact with Moscow RJF94 and/or Vladivostok RCH84
Don't expect to hear littoral operations, tugs, repair ships, etc on hf as they will likely be using v/uhf.
RN Submarine Squadrons
Base/Call Unit QTH/LAT/LON Function
GADZHIEVO 12th Submarine Squadron 6915N/3320 Maritime Base
OSTROVNOY/RJD80 'SVETLANA' Sea Base
GREMIKHA, MURMANSK-140 4419th Marine Base Maritime Base
LOKANGA Sea Base
URA GUBA 35 km from Murmansk Sea Base
ARA Sea Base
VIDAYEVO 7th Division of Submarines Maritime Base
NERPICH'YA 18th Division of Submarines ZAPADNAYA LITSA Sea Base
BOLSHAYA LOPATKA ZAPADNAYA LITSA Sea Base
MALAYA LOPATKA ZAPADNAYA LITSA Sea Base
YAGEL'NAYA 24.31 Division of Submarines SAIDA bay Maritime Base,
ANDREEV Sea Base
TERIBERKA Sea Base
PECHENGA conventional submarines and escorts Maritime Base
OLEN'YA Sea Base
GUBA OKOL'NAYA/RIQ88 Sea Base
VLADIMIR PORT Sea Base
BELOMORSK Kola Flotilla, surface ships and underwater Sea Base
Tiksi/RLU8 Sea Base
Monitoring Russians afloat was perhaps more interesting and easy back in the days when there was an insane amount of Russian Merchant Marine traffic on hf.
No matter what time of day, you could find some poor faktori/akademik/ryba ship sending messages back home for crew or admin even when the bands were dead. They used cw, but much traffic was in the form of radiogramma, radiograms, sent via BFSK SITOR. If you had a PK232 with the SIAM rom you could copy in 3rd shift Cyrillic if you wanted, I did sometimes but much more often simply used ITA2. In ITA2 mode, Russian words would in many cases almost be translated into something an English speaker could understand, and could follow the message gist. If it was a kryptogrammy being sent, it was 5F groups so don't waste your time.
One always kept in mind that being a totalitarian state, every soviet merchant ship was a military vessel, kinda like how most soviet airliners had jumpseats for paratroopers. "Trawlers" were often festooned with myriad m/h/v/uhf antennae, sure they had to fish, but the kgb/gru crew members ran the elint gear below decks trolling for signals while the rest of the crew cast nets.
This every trawler = a RN AGI mentality pissed off a lot of the five eyes units tasked with monitoring every Russian ship afloat, no matter how small and/or boring its activity.
https://en.wikipedia.org/wiki/Five_Eyes
But NSA had to have the data, knowing that if it rated a trawler it was obviously something the soviets were interested in, thus something NSA was interested in.
Hard to imagine the fortune and lives spent on this crap.
I must admit SITOR worked pretty good for the most part and seemingly links much faster and more reliably than many ARQ modes used even today, but it's not as hardy a mode or as fast as the newer stuff. The Russians liked SITOR so much they devised their own modifications to it beyond 3rd shift Cyrillic and used it when everyone else had gone to other means. Now I suppose a lot of Russian MM traffic is via satphone text and voice.
Who knows, you might someday monitor "The Kuz" (Kiev Class Aircraft Carrier Admiral Kuznetsov), or the "Yuri D" (Borei-class submarine Yury Dolgorukiy)
“Tremble, bourgeoisie! You’re done with!”
----------------------------
RN Naval Digital Modes
----------------------------
T600
https://www.sigidwiki.com/wiki/CIS-36-50
http://www.wavecom.ch/content/ext/DecoderOnlineHelp/default.htm#!worddocuments/cis3650.htm
T600 (and derivatives, of wich there are several, some in use by other RN forces) is the actual name for the modem, it's also called BEE and 36/50 by hobbyists
While a Baudot decoder will print on T600 sigs, it's not Baudot code so one needs a decoder crafted for T600.
Apparently T600 employs 3:4 encoding for error check, similar to SITOR in that respect. I suppose T600 is the most common RN digital (non cw) mode on hf.
Some of these T600 freqs are up continuously as a kind of channel marker, idling (looks like reversals to a Baudot decoder) until a message arrives, others only send when there is traffic, at H+10, 20, 30, 40 & 50:
Simulcast T600:
1. 10712, 11088, 15778, 16808, 20536, 22413
2. 5890, 9224, 11524, 14581, 16207, 19688, 19936
3. 14192, 16234
RDL cw and T600:
(simulkeyed with 21.1) 8130, 10164 6. 3196, 5846 7. 5178, 8436
(simulkeyed with 18.1) 3363, 3861, 4043, 4446, 4582, 4602, 5268, 5438, 6342, 6962, 7657, 7816, 8488, 8508, 9346, 10452, 10535, 11468, 12098, 12631, 12741, 13032, 14411, 14664, 15768, 15871, 16912, 17460, 18764, 19210, 20096, 22864
The cw traffic is comprised of opchat between the ends of the link using mark or space as the cw carrier, normally taking place before, between, and/or after T600 traffic. This opchat may have interesting tidbits and is sole reason some monitors watch T600 channels.
Commonly heard in US;
14411, 14664, 16206, 16808, 17460
For an up to date list of T600 channels you will want to get the latest logs from udxf.io or similar hobbyist websites.
That being said, one of my goto T600 channels to watch as a prop indicator is 11039.
Rivet is a free to use decoder often used by hobbyists to decode RN Navy digital traffic, and supports these modes;
Baudot (various speeds) : Used by amateurs , weather stations and other users.
CCIR493-4 : A HF selective calling mode
CIS36-50 (50 baud only currently) : Used by the Russian Navy.
CROWD36 : Used for Russian diplomatic and intelligence messages
FSK200/500 : Used for Russian diplomatic and intelligence messages
FSK200/1000 : Used for Russian diplomatic and intelligence messages
FSK (raw) : For advanced users to investigate unknown FSK modes
GW FSK (100 baud) : A commercial ship to shore data system.
XPA (10 and 20 baud) : Believed used for Russian intelligence messages.
XPA2 : Believed used for Russian intelligence messages.
https://github.com/IanWraith/Rivet
AKULA
- a signal of national communications "SHARK", used in the Navy. Suffice it to the old system, the transmission is encrypted, of the characteristics, the preamble begins with twice the "plus" in terms of duration, spacing is exactly equal to twice the speed of manipulation, and manipulation without breaking phase.
(Band Width) ~1800 Hz
(Low Range) ~500-600 Hz, SBB
(Baud Rate) 500 Hz
(Carriers) 2
(Shift) 1000 Hz
(RX mode) SSB
AKULA-II
Band Width) ~900 Hz
(Low Range) ~250-300 Hz, SBB
(Baud Rate) 500 Hz
(PSK Carriers) 2
(Shift) 500 Hz
(RX mode) SSB
The above Akula info translated from the RUScanner webpage
Akula = shark in Rossii
The Akula modem is a phase coherent BFSK burst modem used by submarine and surveillance forces of the Russian Navy. I suppose the subs can either deploy a vertical from conning tower, towed buoy, or water jet antenna to send via, but 15kw on hf to a trailing wire antenna a meter or so below surface might do too.
The Akula-II modem is a complex, dual-channel Differential BPSK burst modem.
http://staff.ustc.edu.cn/~jingxi/Lecture%209_10.pdf
"Dolphin" is a minor variation of the Akula radio mode(s)
"Ishmael" and "Dnieper" was similar
Parse ASCII transparent charset and synchronous framing or raw bits to view transport and payload.
Akula ACF; 1356 2594 2713
Traffic has/may consist of 10 five-digit groups, time in the air - 0.72 seconds (in closed mode).
RN Submarines have employed up to 15 kW output power in Akula mode.
Akula messages received by shore stations are instantly relayed to the CIC of the RN on all available communication channels. Akula has also been noted in use by surface "recon" ie surveillance units and might be a method used for transmitting emergency traffic of flash precedence by Akula equipped RN units.
Akula messages are copied via 135 radio reception centers of the Russian navy, keeping in mind submarine-related comms have highest priority in Russian Navy
A short BPSK burst is seen before BFSK Akula traffic commences, I presume this is indication Akula-II hardware is in use. I also presume Akula is based on WW2 German efforts to do the same thing, covertly send messages from submarines to HQ on hf;
https://en.wikipedia.org/wiki/Kurier_system
However the kurier system was more or less just very fast morse, its main benefit in reducing the amount of time a signal was ota, thereby reducing chances of discovery and direction finding. The main problem with short duration hf comms, other than propagation, is a noise burst can take out a portion of or entire short communications burst, not to mention bit smearing from multipath that will likewise also be present to one degree or another.
Buy you an Akula modem!
https://www.speechpro.ru/product/voennaya-produkciya/ustrojstvo-peredachi-informacii-r-758is/specification
------------------------------------------------------------
Akula product info;
"Information Transmission Device R-758IS (Akula)
General information
Group of operation 2.3.1, 2.1.1, 2.2.1 GOST RV 20.39.304-98 (GOST RV 20.39.304-98 is somewhat akin to ACP and/or STANAG but for Rossii)
Entering and correction of reports using the keyboard with control on the built-in display
Creating and storing a list of standard reports
Archiving of the transferred reports in non-volatile memory
Built-in automatic self test system
By connecting compatible with existing equipment
Specifications
Power supply 220v with a frequency of 50/400 Hz
40W maximum power consumption
Weight 3.6 kg
Dimensions (width X depth, height), mm 220x285x75 (without shock absorbers)
Full appointed service life of 25 years
Warranty period of 5 years"
---------------------------------------------------------------
Speech Technology Center, LLC (Akula Manufacturers)
Year of foundation 1990
For contact
196084, St. Petersburg, Krasutsky street, 4
Tel .: (812) 325-8848, Fax: (812) 327-9297
Website: www.speechpro.ru
E-mail: info@speechpro.com
Administration Khitrov Mikhail Vasilyevich - General Director
Main activities
development, production; sale; research activities
Own production
multichannel digital black boxes P-424M and P-425M, installed on submarines, ships of the Navy and on airplanes;
Information Transmission Device R-758IS - preparation of data for the transmission of digital messages in the modes: "Shark", "Splav-Info", "Integral", "Splav P-608"; Morse Code Sensor (KM) - a mock-up sample that has been tested on ships of the Navy
Supplied Products
multichannel digital black boxes P-424M and P-425M, installed on submarines, ships of the Navy and on airplanes;
Information Transmission Device R-758IS - preparation of data for the transmission of digital messages in the modes:
"Shark", "Splav-Info", "Integral", "Splav P-608"
Services
performing particularly complex phonoscopic examinations and studies
------------------------------------------------------------------
Speech Technology Center product "Integral" is the corresponding receiver/sensor for Akula modems.
Speaking of Russian Radio Hardware....
This was noted in Fritz Nusser's excellent piece on RN/CIS Navy;
"R-608N / R-608P Emergency Radio Set
HF transmitter/receiver for use onboard surface ships and submarine on the emergency frequncies of the Navy.
Frequency range;
3.6 ... 3.8
4.5 ... 4.7
6.1 ... 6.3
8.2 ... 8.4
10 ... 10.3
12.4 ... 12.7
16.5 ... 16.8
20.0 ... 22.4
MHz with 10 fixed frequencies.
Output power 20 W (70 W short time)
Modes A1A, R3E, H3E, F1B.
Manufacturer is Russian Inst. for High Power Radio Engineering OJSC (St. Petersburg)"
If they sell these things on the open market without changing their freq ranges they just told us where to look for their emergency frequencies.
AT-3004D
This aging PSK/MFSK/OFDM modem is in use by RN forces and is likely or has been replaced with newer and more capable equipment AT-3104. That being said, it's all over the spectrum in use by Russian Navy for the most part I presume the 3104 is backward compatible with 3004.
Traffic consists of text/data and encrypted voice.
http://priyom.org/military-stations/russia/at-3004d
https://www.sigidwiki.com/wiki/CIS-12
Something to consider is that while elite RN forces, submariners to flyboys, often get the newest and most advanced weaponry and electronics, elements farther back from the point of the spear have to make do with perhaps obsolescent and certainly older equipment, eventually as more advanced gear comes into the TOE (table of equipment) more units will be so equipped.
They've developed some neat gear, they just can't afford to make a lot of it right now.
This technology trickle down theory has always been the case apparently. For example, in the late 50s and early 60s as Akula was being developed and tested in the field, only certain subs got the equipment, no surface units had it until much later, like into the 90s. This likely coincided with the desire for RN forces to fight war in a nuclear environment, meaning to be able to fight in a contaminated battlefield, and have the equipment to enable one to do so.
This is one reason why the changeover from tube type electronics to solid state is slow in the going, as tube gear has a much greater tolerance to emp. Today I presume most electronics in RN Navy use to be solid state, and to have emp protection devices and protocols in place to protect said solid state devices.
Today you can actually buy an Akula modem from the maker in Russia, so why not equip every unit with the best and newest at least for compatibility's sake? Perhaps Russia is counting on commercial orders to ramp up production of gear and hide the cost in the volume sold, kinda like having your enemy buy your weapons for you. Wonder what the world market for a hf burst modem is. Also from the pics they're not very small and are likely heavy, I suppose the waveform could be written into a pc app for tx/rx.
Testing and development of new systems, communications and weapons both, is taking place in actual combat in places like Syria, and I wouldn't be surprised to find it in use in the Yemeni/Saudi war. Slcms launched from RN subs have overflown Iran to get to targets in Syria - a test and a message sent to the west at the same time. New tanks and antitank missile defense systems are being tested in Syria too. RN has port facilities at Tartus and Lataika Syria, ringed with S400 air defense artillery systems.
Wouldn't come as a surprise to find the recent incidents where US warships went off course and ran into other shipping was due to RN electronic warfare units testing new toys. Eastern Ukraine is also a testbed of Russian EW gear. Iran dropped a US drone and reverse engineered it because Russia gave them the means to capture the drone.
Resources on the topic;
Tony's excellent piece on Monitoring the Russian Navy
https://planesandstuff.wordpress.com/2015/07/02/monitoring-the-russian-navy-part-one/
RN Navy calls;
https://planesandstuff.wordpress.com/russian-navy-callsigns/
Fritz Nusser's excellent piece on RN/CIS Navy
http://www.udxf.nl/Russian%20navy.pdf
credit due all who have shared and taught what they have discovered to aging itching ears
-
Much traffic generated on CIS naval nets is comprised of position and local weather reporting, they seem to follow the reporting guidelines in this publication;
https://www.jcs.mil/Portals/36/Documents/Doctrine/pubs/jp3_59.pdf
-
Very nice info, Josh.
Interestingly enough, 7630 kHz is also one of the nationwide/regional net frequencies for the Civil Air Patrol (listed as part of "Net 3" but part of their main HF-SSB channel lineup.
-
CAP and the Russian Pacific Fleet likely never bump heads, but it could happen if/when both ends are in darkness.
The most often propagating freqs for CIS Naval cw is 12464 (in use 0600 to 1800) before 1800Z and 8345 (1800 to 0600) after, some fool in Moscow messing things up for me. This timing is problematic as 12 is just starting to come in well when they switch to 8mHz wich often isn't propagating from there that early.
CIS Navy calls;
https://planesandstuff.wordpress.com/russian-navy-callsigns/
-
12464 was finally coming in with some sporadic traffic today, starting at 1500Z. Propa has been lousy lately. Cochannel with the cw traffic was intermittent weak ssb voice. Almost every xmission started with VVV and then rose and fell as propagation teased me.
Next time will have something with a waterfall listening to the traffic, that would make copy a lot easier despite interference and fading.
Rig was the illustrious IC775 with the DSP APF cw filter activated, resulting in a rather spectacular 80Hz bandwidth without much ringing at all. I was concerned that narrow of filtration might be keeping me from hearing those stas off freq, and it'd not take too much freq error to drop them off the edge of the filter, but considering the fading and interference I think the filter made the difference between being covered by cochannel plus bandnoise and a cw note.
I suspect a vertical will be best for this kind of game due the lower angle of reception, especially compared to a short ocfd aligned vostok (east) and zapad (west) when it should be aligned sever (north) and yuk (south) for best priyom (reception) of them rooskiis. I'm really strellyat (shooting) myself in the noga (foot) with this antenna (antenna).
-
Finally caught some traffic on 8345 this morning a bit after 0600Z when they're sposed to switch to 12464 for the day. Traffic was passed for several minutes, so the day/nite switchover time seems to be a suggestion rather than a maxim.
Got up late so didn't get anything from the greyline on 12464 like normal and thought the game was over, but was surprised to catch a lot of very weak cw a bit after 1400Z.
8345 CW 0206Z 08DEC19
QSA? DE RCJG QRU k NR 195 RPT 1 K
-
8345 1415Z 09DEC19
VVV de RCJG QSA1 QRU K
1421Z
RCJG N722 RPT AR
RCJG RPT AA1 AR MO K
RCV de RCJG N1 772 RPT AR
(RCJG wants RCV to repeat 772)
1427Z
RCV de RCJG NR722 RPT K
1613Z
VVV RCA RCA de RCJG QSA? QTC K
=sml= (5f groups)
77392 etc
8345 0600Z 10DEC19
VVV RCV RCV RCV de RCJG RCJG QSA? QTN
RCV de RCJG QSA1
de RCJG REO QSA?
0615Z
de RCJG RCJG
0618Z
VVV RIW RIW RIW de RCJG RCJG QSA? QTC K
(then into 5f groups)
this guy had problematic element spacing
RCJG is the Ivan Bubnov, a Boris Chilikin class tanker of the Black Sea Fleet
http://www.shipspotting.com/gallery/photo.php?lid=1091287
-
8345 CW active now 2019z 12/12/19. no interpreter running.
BTW, thanks for all the work you put into this thread Josh.
-
8345 CW active now 2019z 12/12/19. no interpreter running.
BTW, thanks for all the work you put into this thread Josh.
Glad you find it interesting, it's my tribute to those who taught me, and there are many.
On cw interpreters, here's an video on the subject comparing several;
https://www.youtube.com/watch?v=MRuFn1nnuoY
I find that decent code with no multipath can be correctly copied by the usual sorcerer and etc software decoders, but once a bad fist, qrm/qrn, or multipath appears, it takes a human to make sense of the mush. It's odd but you can hear multipath on a cw note after you've been doing it a while.
Worse yet is Russian Navy doesn't seem to issue keyers to its forces, it issues straight keys, meaning every operator is going to have their own element timings.
Found out the Bubnov is sitting off the coast of Morocco at the moment, so plenty of opportunity for multipath from there to here. Hearing RIW Moscow or RCV Sevastopol is sure to have multipath too.
Speaking of Moscow and Sevastopol, 12464 and 8345 are the primary ship to shore side of the duplex channel, the shore to ship side are;
RIW Moscow 9145, 11000, 14556
RCV Sevastopol 15586, 7566
I've compared several decoders; sorcerer in two versions, K500, WCODE, CW Get, and CW Decoder and they all pretty much perform about the same, perhaps CW Get is a bit better, while WCODE will translate Cyrillic morse - wich I am not good at at all. I let them run overnite or when I'm away or listening to something else with another rig.
One thing I noted is most all of them want about 15 percent cpu time, a bit high to my thinking, setting CW Get to 50 cw signals reduced it to 4 percent, much more to my liking.
CW Decoder dl;
https://download.cnet.com/CW-Decoder/3000-18511_4-75325058.html
Sorcerer dl;
http://www.kd0cq.com/2013/07/sorcerer-decoder-download/
One thing I find useful is to set the input freq of the decoder app to twice the cw note freq.
For example, I always employ 600Hz bfo offset, all cw copied ota will be at that 600Hz tone. Setting the decoder to 1200Hz will allow the second harmonic to trigger the decoder rather than the actual tone at 600Hz plus all the band noise, of course one must make sure a second harmonic is present in the app for this to work - you will verify it in the fft when signals are present. The 1200Hz second harmonic will be pretty much completely free of band noise.
I've been thinking about a means to a better decoder app, one that perhaps employs a pll to;
1 detect a sinewave
and
2 to ensure phase coherence wich will also enhance noise rejection (noise is incoherent) and define elements.
(Not that I know how every decoder works)
Then to have a buffer to copy elements into and look for the averages of an individual senders keying, dits, dahs, spacing, then apply these globally to the message for its entirety -- the above is why humans are better cw decoders than machines as we do all this without thinking about it.
I suspect that a decoder written with these features could decode cw that's beneath the noise floor, and humans can't do that. Smolinksi, I'm looking at you.
You could even determine/identify individual senders this way but that has been done for ages.
Lol using massive compute power of the most complex and modern design to decode the simplest of digital codes, dits and dahs, ones and zeros.
-
8345 0647Z 13DEC19
VVV RIW RIW de RMUW RMUW RMUW NR 63 RPT K
0644Z RMUW RPT
0659Z VVV RIW RIW de RMUW RMUW QSA? K
0700Z RMUW RPT NR 63 RPT QSA?
0702Z RMUW RPT (then into groups)
99360 70060 (errors) 92610 K
0704Z RMUW OK QRI
RMUW is the Shakhter (SB-922), a Sliva class salvage tug of the Black Sea Fleet.
https://www.vesselfinder.com/vessels/SHAKHTERSK-3-IMO-7038642-MMSI-273397210
https://www.vesselfinder.com/?imo=7038642
not too shabby dx for a tiny bobber off the east coast of Russia
-
8345 0440Z 14DEC19
RMUW NR 393 RPT K
0445Z RMUW IIII QSL 393 K
0603Z RIW de RCJG QSA? K
RIW de RCJG =SML= (groups)_
0607Z RCJG RCJG RPT K
RIW de RCJG QSA? K
-
0610Z 16DEC19
RCJG (groups)
0612Z RCJG RPT QTC K
RCJG RPT K
0613Z RCJG OK
0615Z de RMUW RMUW QSA? K
RJH45 RJH74 (groups)
0622Z VVV RCV RCV de RMUW QSA?
RMUW was requesting RCV pass a wx report to the following;
RJH45 = MOSCOW NAVAL METEO
RJH74 = NORTHERN FLEET METEO
-
8345 0652Z 16DEC19
FOR RJH73 (groups) de RCJG
RPT 020
8345 0611Z 17DEC19
VVV RCV RCV de RCJG QSA? K
0612Z VVV RCV RCV de RCJG QSA? K
0615Z two stations sending same time, many outstations (ships) are on this duplex net that will not be able to hear each other due propagation but the controls (shore stations) will be able to exert some order on the net
0616Z RMUW RMUW
0617Z VVV RIW de RMUW
0620Z RMUW OK QRU K
0622Z VVV de RMUW QSA? QTC K
12464 1508Z 17DEC19
VVV RIT RIT de RHO62 QSA? K
1515Z VVV RIT RIT de RHO62 QSA? K
1517Z VVV RIT RIT de RHO62 QSA? K
1524Z VVV RIW RIW de RHO62 QSA? K
1526Z VVV RIW RIW de RHO62 QSA? QTC K
1528Z VVV RIW RIW de RHO62 QSA? QTC K
1531Z VVV RMP RMP de RHO62 QSA? QTC K
1532Z VVV RMP RMP de RHO62 QSA? QTC K
1541Z VVV RMP RMP de RHO62 QSA? K
1546Z VVV RMP RMP de RHO62 QSA? K
1548Z VVV RIT RIT de RHO62 QSA? QTC K
1543Z VVV RIW RIW de RHO62 QSA? QTC K
RHO62 is the ADMIRAL VLADIMIRSKIY, an Akademik Krylov class survey/research ship of the Baltic Fleet, apparently the last of her class in service
https://commons.wikimedia.org/wiki/Category:Admiral_Vladimirskiy_(ship,_1975)
https://tass.com/defense/985205
-
0706Z 18DEC19 VVV RIW RIW de RHO62 RHO62 QSA? K
1200Z VVV RIW RIW de RCJG RCJG QSA? QTC K
1209Z VVV RIW RIW de RCJG RCJG QSA? QTC K
1216Z VVV RIT RIT de RHO62 RHO62 QSA? K
1217Z RIT RIT de RHO62 RHO62 FOR RJH74 =SML= (goups)
1221Z VVV RIT RIT de RHO62 RHO62 RPT NR 10 K
1222Z VVV RIT RIT de RHO62 RHO62 RPT NR 10 K
1222Z VVV RIT RIT de RHO62 RHO62 OK QRU K
Seems I'm at just the right spot to hear RCJG and RHO62, wonder when some other calls will come along.
Something to keep in mind is the Ivan Bubnov will be in the company of a task force since she carries petroleum for the fleet, she replenishes the fleet allowing them to stay on station far longer than is she weren't present. When the Kuz (https://en.wikipedia.org/wiki/Russian_aircraft_carrier_Admiral_Kuznetsov) was plying the waves and not on fire in drydock like recently, Bubnov was in her entourage.
-
8345 0647Z 13DEC19
VVV RIW RIW de RMUW RMUW RMUW NR 63 RPT K
0644Z RMUW RPT
0659Z VVV RIW RIW de RMUW RMUW QSA? K
0700Z RMUW RPT NR 63 RPT QSA?
0702Z RMUW RPT (then into groups)
99360 70060 (errors) 92610 K
0704Z RMUW OK QRI
RMUW is the Shakhter (SB-922), a Sliva class salvage tug of the Black Sea Fleet.
https://www.vesselfinder.com/vessels/SHAKHTERSK-3-IMO-7038642-MMSI-273397210
https://www.vesselfinder.com/?imo=7038642
not too shabby dx for a tiny bobber off the east coast of Russia
Is it?
"Shakhter" (ex-SB-922) is now RFS Shakhtyor (Шахтер) - IMO 8406652 call sign?
Black Sea Fleet
https://nok-schiffsbilder.de/modules/myalbum/photo.php?lid=46419
-
8345 0607Z 19DEC19
VVV VVV RIW RIW RIW de RCJG RCJG QSA? K
RIW RIW de RCJG RCJG FOR RJH45 =SML= (groups) K RCJG
0613Z VVV RIW RIW RIW de RCJG RCJG QSA? K
0623Z VVV RIW RIW RIW de RMUW RMUW QSA? K
1432Z 12464
RCJG RPT (groups)
1422Z RCJG QRU K
1502Z RIT RIT RIT de RHO62 RHO62 QSA? QTC K
1509Z RIT RIT RIT de RHO62 RHO62 (groups)
1514Z RIT RIT RIT de RHO62 RHO62 QSA? OK QRU K
1629Z VVV RIW RIW RIW de RCJG RCJG QSA? QTC K
1630Z RCJG RPT (fade) S6109 8654T
1631Z RCJG RPT K
1632Z RCJG RPT K
1634Z VVV RIW RIW RIW de RCJG RCJG NO K
1635Z RCJG QRU K
1636Z RCJG QRU K
-
8345 0647Z 13DEC19
VVV RIW RIW de RMUW RMUW RMUW NR 63 RPT K
0644Z RMUW RPT
0659Z VVV RIW RIW de RMUW RMUW QSA? K
0700Z RMUW RPT NR 63 RPT QSA?
0702Z RMUW RPT (then into groups)
99360 70060 (errors) 92610 K
0704Z RMUW OK QRI
RMUW is the Shakhter (SB-922), a Sliva class salvage tug of the Black Sea Fleet.
https://www.vesselfinder.com/vessels/SHAKHTERSK-3-IMO-7038642-MMSI-273397210
https://www.vesselfinder.com/?imo=7038642
not too shabby dx for a tiny bobber off the east coast of Russia
Is it?
"Shakhter" (ex-SB-922) is now RFS Shakhtyor (Шахтер) - IMO 8406652 call sign?
Black Sea Fleet
https://nok-schiffsbilder.de/modules/myalbum/photo.php?lid=46419
Thanks for the info, also far as I've seen there are three of the class with the same name and a numeral, I've no clue exactly wich is ota when I catch them.
-
1528Z 20DEC19 VVV RCV RCV RCV de RHO62 RHO62 QSA? QTC K
(groups)
lotsa errors, had to guess at some words but we know the message format so no worries, just need the calls
1530Z 20DEC19 VVV RCV RCV RCV de RHO62 RHO62 QSA? QTC K
(groups)
1534Z 20DEC19 VVV RIW RIW RIW de RHO62 RHO62 QSA? QTC K
multipath was bad, lotsa dit and dah smearing even with the noise floor at -130dBm and sigs at -125 or stronger, preamp got the floor down to -140 but didn't help, neither did wider filtration
-
8345 kHz
12/21/2019
0546z through 0652z, intermittently.
no decoder running
-
Here's a wav recording of this morning's proceedings;
https://www.filemail.com/d/ugvoyeksutfilgp
The 1400Z take was right at greyline and very weak, the 1500Z take was better, however you can tell when they switched ops or the same op reduced speed, they had a few repeat sessions and that may be why they reduced speed.
Think I got the entire session, but had to be fast on the pause button to reduce file size so some characters at the beginning of each sentence may be missing.
There was random othr as well as other noises present but the band for the most part was quiet. Rig was a Xiegu G90 at 100Hz filter, antennae an ocdf, recording done by WCODE.
Conditions were -127dBm noise floor with up to -110dBm signal levels.
Still listening to 12464 @ 1615Z and an incredibly weak sig is just making it over the noise, so propa from there to here seems done for the day on this band.
-
8345 kHz
12/21/2019
0546z through 0652z, intermittently.
no decoder running
No copy here due local rfi source on 8345 at that time, but keep up the good work, you'll be decoding in no time!
-
8345 kHz
12/22/2019
0603z through 0619z, intermittently.
no decoder running
-
Some who follow the RU Navy on hf say there is no distinct and absolute transition from day to night freqs as I've noted for 0600/1800, that stas will use whatever frequencies are propagating.
That stands to reason, however I note a distinct lack of traffic on 8mHz after about 0700 and 12mHz after 1900, so they do qsy near those times as far as I'm concerned.
What must always be kept in mind is what stas the ships are trying to contact, thus if those stas are in daylight or not, and weather there's a need and/or possibility for long haul (higher freq) or nvis (lower freq) hf comms.
Apparently in an effort to enhance signals security, much cw traffic has been moved from long haul to more nvis and localised networks, as well as satcom. Meaning instead of 12464, 8345, and other ranges noted for reliable long distance propagation, they're all down in the 3 and 4mHz range.
This effort to enhance signals security is problematic for us eavesdroppers located far away from the ships and their respective shore stas.
Earlier today (too lazy to get out from under warm covers to see what time it was and convert that to utc or moscow time) on 8mHz, RMUW was calling RIT, RCV, and RIW in turn and not getting any response for all I can tell, as RMUW had traffic to pass but apparently no shore station heard him so no groups were sent on 8mHz. They might have had success on another freq but I didn't copy any.
This series of reality show (ie scripted) vids has some really neat hardware as well as underway operations of interest to anyone who follows RU Navy;
https://www.youtube.com/watch?v=XhCGtc4kWDQ
-
8345 kHz
12/23/2019
0209z - almost non-stop past ten minutes
no decoder running
Josh, I replied to your PM.
-
0329Z 22DEC19 8345 VVV REO(?) de RHO62 RHO62 (groups)
0408Z " "
0620Z VVV RIW RIW RIW de RHO62 RHO62 QSA? QTC K
1527Z 23DEC19 12464 VVV RDV RDV RDV de RHO62 RHO62 QSA? QTC K
-
8345 kHz
12/29/2019
0020zulu - almost non-stop past thirty minutes
no decoder running
-
12464 kHz
12/29/2019
1650z, 1658z - brief transmissions
no decoder running
-
When you hear traffic on 8345 or 12464 look for the other side of the duplex channel on the following freqs;
RIW Moscow sends to ships on 9145, 11000, 14556
RCV Sevastopol sends to ships on 15586 day and 7566 night, with weather reports also on 5915, in the past on 10543
RIT Murmansk (artic circle) 5343, 7467, 11155
RAA St Petersburg 8120
RJS Vladivostok (pacific coast of Russia) 4048, 5411, 7632, 10203, 13636
RIW, RIT, and RCV are the most commonly copied hq calls heard here, so whoever is called by the ship being monitored, look for a response to their call on the designated channels.
The top two are also the most likely to be heard here due their locations, I don't expect to hear RJS Vladivostok (means something like Ruler of East) at all for the most part due the distances and would be surprised if I could hear RIT Murmansk.
-
Thanks Josh.
-
The part of the 12mHz band we listen to is populated with many strange creatures (other than ourselves of course).
From Piscadors in Spanish ssb to various other maritime assets communicating, for example at 12577.0 kHz (tune 2kc lower to decode) we have a global gmdss freq that sees a lot of traffic.
Another frequent visitor is a othr of some type who often plops their doppler correction/equalizer training tone right on 12464, when he's on freq you hear the letter O sent in slow morse and then a burst of radar fart, when he's off freq you just hear the fart.
The portion of the 8mHz band we tune to also has nearby non-naval maritime cw freqs that are still active in addition to the CIS Naval channels. It also sometimes gets a visit from a radar/fart and loads of pescadors pescadoring.
This extraneous traffic is why a rig with a fish finder (panadapter display) is so wonderful for the hobbyist, you can see what is going on around you, and in most cases identify the type of signal without tuning to it.
In the near future the sdr will be hooked back up to the tenna so multiple vrx operation can ensue, being able to copy both sides of a duplex net without having to switch vfos will be interesting. In the past, pros (men from US Army, Navy, and Air Force on loan to NSA) would stand watch for hours with two or three R390As sitting in front of them, one R390A tuned to the outstation (in our case the ships) and another R390A tuned to the control (Naval hq), with the other R390A (in the case of the lucky ones who had 3 R390As) tuned to a hfbc station playing current rock music, shoes off and cup of coffee in hand, copying morse traffic by pencil or on a mill (typewriter). Their logs would then be sent to NSA and the various commands who wanted the traffic, today we just want to see who we can hear, however NSA (and other sigint orgs around the world) watches us and our logs too. Hi guys!
-
The catch has been mighty slim last few days trawling for soviet signals. Wonder what that old gorby is up to.
https://twitter.com/US5thFleet
-
I’ve noticed the decreased traffic too. I wonder if they’ve moved to less-well-known frequencies because of the current situation?
-
Might be, they had a black sea exercise not too long ago that may have kept them busy as President Putin was there overseeing everything.
We might rationally expect to see daily traffic from the Shakter as it's a "research" vessel, but perhaps not from the Bubnov as the Boob (heh) will often be on ops with the fleet - aka the reason she exists, in such cases she likely sails under hf emcom (emission control aka radio silence) as far as sending wx reports we've been copying of late.
In general, when you hear QTC in the traffic it means there's a message to pass. usually wx/sea state related.
-
This guy has some detailed posts on the Russian Navy & decoding some of the weather reports (ones using the FM-13 format).
https://planesandstuff.wordpress.com (https://planesandstuff.wordpress.com)
-
Thanks Boriken.
His article on using SDR Console’s analyzer for use on russian navy frequencies was especially interesting.
-
This guy has some detailed posts on the Russian Navy & decoding some of the weather reports (ones using the FM-13 format).
https://planesandstuff.wordpress.com (https://planesandstuff.wordpress.com)
He's one of my elmers on all things rooskii.
-
https://www.youtube.com/watch?v=RyMea4DbglU&feature=emb_title
black sea drills
https://www.youtube.com/watch?v=tpvq3hmCKCs
background music for above black sea vid, gorby approved
-
Now that the storms have passed, I plan to leave the 9k on 12464 until 1800z. ( Unless the NY transatlantic op with the nails reappears ;) ).
-
Was in the other room and had forgotten to switch the rig to 8MHz @ 1800 when a burst of about 30wpm morse started on 12464 @ 2222Z, long after the usual switch to night primary on 8mHz. It had a very bad auroral zone flutter to it, making it very hard to read. Lasted about 10 mins and that was it, Moscow time was 0122.
Earlier today saw why there'd been no traffic noted on 12464 the last days or so, it was tuned to 12364.
LOL
have fun with your 9000!
-
12464 30wpm or faster cw 2348Z 12JAN19
in the noise but much more stable than the last tx
-
Nil heard on the usual haunts lately, so will be trying for RIT's radio prognoz bcast on 7422, 1000/2200Z daily.
Prognoz, indicating prognosis or forecast, is the Russian navy's determination of what the ionosphere will support as far as HF comms are concerned. The tx is somewhat cryptic as there is dissent on how to read the bcast but it's likely date/time and channel designators rather than an encoded frequency list, but like said, dissent rules the day.
-
i haven’t heard anything either Josh, so I’ll be interested to know what you find.
-
i haven’t heard anything rither Josh, so I’ll be interested to know what you find.
Lol I was hoping you'd catch this post before 2200 and tune in!
-
Thank you, however I’m about to leave babysit my granddaughter so i’ll miss this pass.
-
Ah well, always next time.
Also for unattended monitoring been looking into these gizmos;
https://www.ebay.com/itm/Morse-Code-Reader-CW-Decoder-Morse-Code-Translator-Ham-Radio-Essential/372858119170?hash=item56d0136402:g:Gu0AAOSwPkhd4KL7
cheap and if given decent sending they do a fair job, and don't have to leave a pc on to just decode cw.
Have to find the vid where the guy found out what control does what as apparently they have some controls that aren't detailed.
-
There is this:
http://www.f6hoy.com/cw/
Or this:
https://youtu.be/PnJTHTvBUPg
Is that what you were thinking about?
-
A posting on eham claimed that the Chinese CW decoder is based on this:
http://www.ik3oil.it/_private/qst_cw.pdf
I have not verified whether that is true or not.
-
Yeah, thanks. There are some hardware decoders that are almost legendary for being able to handle poorly sent or fading code. Nice to have one but not going to spend $150 for a used one, a ten spot I won't miss for one that does the job well enough on good clean signals, plus with free shipping.
This link you provided;
http://www.f6hoy.com/cw/
has more or less what I want to do, put the thing in an altoids can with remoted controls, to keep rfi from getting int or out of the thing as well as protection.
Was considering hacking the front panel of a hf rx that had open space for the display and controls of the code reader, but that then limits its usefulness to that rig alone, even if that rig is pretty much devoted to cw rx.
-
i haven’t heard anything rither Josh, so I’ll be interested to know what you find.
Lol I was hoping you'd catch this post before 2200 and tune in!
Nada heard that day, a look out the window shows plenty of daylight left so really shouldn't expect to hear this, especially with a horizontal, a vertical might stand a chance. 10 minutes till showtime!
-
Heard some CW on 7422 at 2200 but there was too much splatter from the station on 7425 to decode anything that looked logical.
-
VVV RMP RMP RMP de RHO62 QSA? QTC K
RMP RMP RMP de RHO62 =SML= FOR RJH74 and into groups
0705Z 02FEB20
RHO62 ADMIRAL VLADIMIRSKIY
RMP Baltic Fleet HQ
-
Finally some traffic. Which frequency Josh?
-
Lol sorry, 12464 for this one. I keep one rig with decoder tuned overnite to whatever freq has the least rfi, in this case 12464. We need to branch out to the lower freqs, seems they're hiding down there.
2776
3356
3248.5
3500.5
3734
3762
3765 USB voice ship to ship
4635 apparently very active
6290
6346 RIT RADIOPROGNOZ 1000Z
6461.5 RMP duplex with 6494.5
8120 RAA Moscow simplex
11000 RIW simplex from hq to ships
You'll note some of these are in the 80m HAM band, but around here the specific HAM freqs are often quiet, so a catch is possible.
-
thanks josh
-
Around 0900R (ROMEO or Eastern time) on 12464 a beacon started up. At first thought it was sending random letters every 30 secs, lasting for a few hours. I thought it was either poorly sent or poorly shaped cw as the letters had bad spacing but finally it started to come in strong enough to overcome the fading and multipath, it was a single long dash lasting almost 3 seconds.
-
Possible new call, RK9E calling RIW with QSA? and QTC, 1330Z 17FEB20
-
Thanks Josh
12464?
-
Do the Rooskies make a habit of using 80 meters in USB mode? Seems like it’s pretty common for marine purposes (military and otherwise).
I’ve read numerous reports from hams in Europe of Irish fishing fleets, Finnish trawlers, Italian fishermen in the Med, etc. using 3500-4000 kHz in USB mode for ship to ship comms. It’s a good place to hide a military net. Same with 40 meters.
The split frequency operation seems pretty common too.
-
Thanks Josh
12464?
Another oops and yes, 464. I try for two consecutive 100 percent callsigns copied before logging them, but this one had so much multipath and fade the elements were smeared, making it hard copy. The most sure thing was the call had RK in it, lol. They seem to be having about as much trouble as me lately, someone was calling RCV, RIW, and RIT in turn earlier today on 464 before finally finding someone to take his QTC.
TYhis was perhaps an hour before sunrise, so greyline propagashuns, replete with multipath, is my link to whoever is sending me soviet signals!
Send strong soviet signals, tovarich!
-
Do the Rooskies make a habit of using 80 meters in USB mode? Seems like it’s pretty common for marine purposes (military and otherwise).
I’ve read numerous reports from hams in Europe of Irish fishing fleets, Finnish trawlers, Italian fishermen in the Med, etc. using 3500-4000 kHz in USB mode for ship to ship comms. It’s a good place to hide a military net. Same with 40 meters.
The split frequency operation seems pretty common too.
Rooskii militaryskii makes use of upper and lower sidebandskiis, one of the few military that does upper and lower. Not only do they often encroach the HAM bands with their nefarious ways, they also employ calls that are obviously US HAM calls in cw mode, such as N9KT and similar.
That said, these aren't naval calls for all I know, more like army, air defense, air force, or strategic rocket forces.
They also have no problem firing up cluster beacons in the HAM bands as well as gigantor radars.
"Cluster Beacons
A group of radio beacons with single-letter identifiers ("C", "D", "M", "S", "P", "A", "M" and "K") have been regularly reported near 3594, 4558, 5154, 7039, 8495, 10872, 13528, 16332 and 20048 kHz. The term "cluster beacons" is frequently used for them, as they transmit in parallel on frequencies only 0.1 kHz apart. These beacons transmit only their single-letter identifier in standard CW (A1A) using Morse code"
https://www.sigidwiki.com/wiki/Morse_Code_(CW)#Cluster_Beacons
https://www.smeter.net/propagation/beacons/7039.3-k-petropavlovsk-kamchatskiy.php
https://www.sigidwiki.com/wiki/29B6_%27Kontayner%27_OTH_Radar
-
Yay a new call!
VVV RIT RIT RIT de RJS81 QSA? QTC K
0225Z 28FEB20
RJS81 aka the "Gazolin", a PM-82 Amur Class Floating Workshop of the glorious Baltic Fleet. Everyone should have floating workshop, da? Send strong soviet signals, comrades!
and in honor of new callsign priyom
https://www.youtube.com/watch?v=EjZtn_RLdqU
-
Thanks Josh
8345?
-
Lol once again I failed to list the freq, sorry JC, yes 8345. Oddly both main freqs have been fairly propagating lately, but the multipath has been brutal enough to make getting calls other than the repeated shore stations called a tough job.
-
Just glad you’re getting signals, I’ve had little luck or time lately.
Thanks for update
-
A story with pics of the ship;
https://www.dailystar.co.uk/news/latest-news/russian-ships-royal-navy-wildcat-16876800
I presumed it was near Syria and the story seems to indicate its presence there in the past, as the rest of my catches seem to be from that region.
-
RIT RIT RIT de RHO62 RHO62 QSA? QTC K
musta not got a response as traffic did not ensue but nice to hear from moy droog (my friend) RHO02
0614Z 01MAR20
-
Russia is moving a lot of gear to Syria due the recent fighting between Turk and Syrian forces, this may explain the uptick in traffic heard lately.
This transport ship just passed the Bosporus on its way to Tartus;
https://twitter.com/YorukIsik/status/1234496165409959937/photo/2
Check out the antennae, cage dipoles, lots of hf vertical monopoles, crossed loops, etc. Mebbe an elint division aboard.
VVV RCV RCV RCV de RMUW RMUW QSA? QTC K
into traffic but very multipath, odd part is broad daylight here yet sigs were good
2100Z 03MAR20
RMUW is the Schakter petroleum transport commonly found with CIS Naval assets operating off Syria.
-
VVV RIW RIW RIW de RMUW RMUW QSA? QTC K
0357Z 03MAR20
decent sig
-
Reuters' monitoring of the Bosphorus since Feb. 28 shows Russia has sent five warships toward Syria within six days. That exceeds a usual pattern of one or two warships ships per week.
The Russian military announced the departure of the Admiral Grigorovich and Admiral Makarov frigates for Syria, but three other warships have followed unannounced.
One is the Orsk, a landing ship capable of carrying 20 tanks, 50 trucks or 45 armored personnel carries and up to 400 troops. The others - the Novocherkassk and the Caesar Kunikov - are landing ships that can carry over 300 troops, tanks and armor.
Turkey has responded by beefing up its escort protocol for Russian warships using the Bosphorus. Three Turkish patrol boats and a helicopter escorted the Russian frigates - such ships are usually accompanied by a single coast guard vessel.
https://kfgo.com/2020/03/04/russia-reinforces-syria-before-putin-erdogan-talks-flight-and-shipping-data/
this supports the increase in traffic copied lately
-
Josh, most of your hits been on 8345 and 12464? I’ve had zero luck lately.
-
Yep, those two. Might try for naval air on 8816 and the command channels; 11000, 9145, and so on.
-
Thanks
-
Yay a new call!
VVV RCV RCV RCV de RMGB QSA? QTC K then into =SML= FOR RJH45 (groups)
08345 0200Z 05MAR20
VVV RCV RCV RCV de RMGB QSA? QTC K then into =SML= FOR RJH45 RJH73 (groups) RMGB OK QRU K
08345 0603Z 05MAR20
RMGB is the Iman, voice call Prozaik, an Olekma Class Tanker of the Baltic Fleet
https://en.wikipedia.org/wiki/List_of_active_Russian_Navy_ships#Auxiliaries
Apparently this thing's an ancient relic like I am.
-
12464
Mar 06 sometime between 1730z and 1940z
RCV RKV DE RMGB QSA QTC K VVV RCV RCV RCV DE RMGB RMGB QSA? QTC K
-
12464
Mar 06 sometime between 1730z and 1940z
RCV RKV DE RMGB QSA QTC K VVV RCV RCV RCV DE RMGB RMGB QSA? QTC K
Well done! I think I copied this one but the multipath was horrific, it'd be in the noise one element and s5 the next. Noise floor was -128 dB down, sig was -100dB at times.
8345 0600Z 06MAR20 VVV RCV RCV RCV de RMGB QSA? QTC K
8345 0616Z 06MAR20 VVV RCV RCV RCV de RMUW QSA? QTC K (groups) RMUW OK QRU K
QRU = I have nothing for you, add a ? and it becomes do you have anything for me?
And in celebration of a new call;
https://www.youtube.com/watch?v=3kk_oYURQrs
-
Dunno if your 9k does dual watch, where you can copy on two different freqs at the same time. Icom pioneered this methodology with the 781 as I recall, see here;
"The IC-781 was originally designed under a defence contract; the Dual Watch feature is quite well suited to guard-frequency monitoring in the same frequency range, or the monitoring of both frequencies in a half-duplex (split) situation. These scenarios often arise in some military/government HF operations. The utility of Dual Watch in the amateur radio service could well be incidental to the original design intent."
https://www.ab4oj.com/icom/dw.html
In my case the 775 and 756 P2 do dualwatch and I've found that even though there's a bandpass switch when tuning from 12464 to 8345, when the lower tuned freq is the primary it seems to work out well enough. To get the full sensitivity of the rig in dual watch mode on both freqs, those freqs have to fall within the same bandpass filter. The 8345 falls outside the 40m HAM band preslector, wich extends from 6MHz to 8MHz, the next extends from 8 to 12mHz, sadly cutting off 12464, but it still works out fine.
I can copy traffic on both easily enough with dualwatch. The sdrs available here do not cover the range one can employ with dual watch, but they do fine in the bandwidths they do provide for. I suppose most preselection filters in HAM rigs are of the sub-octave pie network type, wich offers a more or less symmetrical bandpass.
https://en.wikipedia.org/wiki/Octave_band
-
Thanks Josh
I don’t remember seeing anything about dual watch in the manual, I’ll check.
( Checked, no dual-watch )
8345 kHz
Mar 06
2137z
RCV DE RMG NE RMGB QSA Z QTCK GMGB HT42 35 7 0025 442 = SM L = 1 7988 77812 31894 332 84 83544 60 5 88 98027 91121 UA812B 51 5 EEE64566 ?0IM56 87787 54765 7 1IO2 3DE137 34683 35173 15846 88491 013TS3 36714 348 UIA 98787 E2TG057 36624 UT0300 50DE15
2J758 70408 10TB 2 V18TISA 24912 0 B033 = AR RMGBK E MI RMGBAPT K RMGBRPT 33 UT8 4 K RMGB RPT K NG RMGB OK X RUK M
8345 kHz
Mar 06
2204z
RIT RIT RIT RIT DE RME 81RME 81 QSA
QSV K RIT RIT RIT DE RME 81RME 81 KSA 1 QS V K
-
Huzzah Another new call!
"RIT RIT RIT RIT DE RME81 RME81 QSA"
Good job Mr Maxwell, you caught the;
RME81, voice call Ladnik, ship/unit name MB-119, a Goryn Class Ocean Tug of glorious Baltic Fleet
http://russianships.info/eng/support/project_733.htm
Stronk soviet signals to you comrade!
https://www.youtube.com/watch?v=lL4KtwR3TKI
bonus
https://www.youtube.com/watch?v=YEt41bYQBgE
-
Thank you sir!
-
VVV RIW RIW RIW de RMUW QSA? QTC K
short groups
RMUW OK QRU K
0010Z 07MAR20
-
Josh, were those on 8345 or 12464? I was on 8345 and missed them.
-
Sorry, was sneaking in on 12464 long after I expected traffic to move to a lower qrg. There may be some traffic on 8345 as someone keeps sending K at random times, I suppose they have traffic of higher priority or other that they want hq to copy.
-
That’s cool, was just curious.
Excuse my ignorance, but are we receiving the message from the ship or the HQ?
Disregard my question, you answered it earlier in this thread.
-
8345 kHz
Mar 07
0217z
DE RMGB RMGB QSA? QTCK R MM TTT
90 50 7 0 5 00 99 0 = SML FOR RIW RCV = 11111 5 6 J 8 22286 24 9 51
5 5 76 7 42158 E M TT M723 TTT TT96 6 6 6 6 8 9 2 0T4 KGD YQX CZB0
M TB813 5 12 108 4 7826 4 125 9 9 1 7 4 6 8615 9 9987A 62 6 M T T M 5005 5 \
4 7 4 32 9 5986 08315 07911 TTO61 45 15178 04 461 TTT TT0336 7 6209 TTT TTGB
OK QR MTT TTO49 070 TZ8 78 2 47 MM093 5 47676 TTM1521 5 7 443 A
96 76 0 88 231 TT4992 1 9434 4 4 5 3 5 19010 84 408 33071 0228 9K
-
I've yet to catch RCV, RIW, RIT, or RMP, the hq stas that use the other side of the duplex channel, perhaps due to lack of decent antennae on my part in addition to the fact those stations are several thousand km further away from here than the ships we can hear routinely. Have to park a rx on them and wait for something to happen.
8345 RME81 FOR RIW RIT RMP etc
0316Z 07MAR20
VVV RIW RIW RIW de RME81 QSA? QTC K
QSL 91912 919?
RME81 OK QRU K
0357Z 07MAR20
8345 VVV RCV RCV RCV de RMGB QSA? QTC K
(two stations are sending at the same time wich sounds hilarious)
RMGB RPT 45
RMGB OK QRU K
0602Z 07MAR20
VVV RCV RCV RCV de RMUW QSA? QTC K
=SML= FOR RJE73 (one of the fleet weather shops)
(groups)
AR RMUW K
0617Z 07MAR20
VVV RIW RIW RIW de RME81 QSA? QTX K
=SML= FOR RJH45 RJE73 (fleet weather shops)
(groups)
0622Z 07MAR20
-
8345 kHz
Mar 08
0010z
(tuned in to a transmission in progress)
9 368 1 T013 41798 V 2806 10120 4MO230 IE2030 EE 0110 870 0
22253 00160 2990 0 OT 013 = AR RMGB T
RMGB NT K
-
All 8345
VVV RCV RCV RCV de RMUW RMUW QSA? QTC K
VVV RCV RCV RCV de RMUW RMUW QSA? QTC K
0611Z 08MAR20
VVV RIW RIW RIW de RMUW RMUW QSA? QTC K
0615Z 08MAR20
RMGB OK QRU K
in groups ongoing
0617Z 08MAR20
More traffic this monitoring session than I've noted before, but it was very weak and mostly a letter here and a letter there.
-
12464 kHz
Mar 09
Around 1500z
RCV RCV DE RMGB RMGB Q21 VK NR 944RPT 2K R OMD EE E A4 RPT 2 4
A HI RMGB SL 9H K
-
Very noice, lotsa traffic lately. I caught RIT being called by RMGB today on 8345 but was too lazy to get out of bed to see what time it actually was. Then RMGB was back around 1pm local with decent sigs.
Urra!
New call noted!
RKB91, the Kola, an Altay Class Tanker of glorious Baltic Fleet
de RKB91 QSA? QTC K
Caught the ship call but not the hq called
0622Z 09MAR20
http://www.vesselofinterest.com/2015/08/following-russian-navy-mod-altay-class.html
in honor of stronk soviet signals;
https://www.youtube.com/watch?v=kmh9TDuLU5g
send stronk soviet signals, brata!
-
12646 kHz
Mar 09
Between 1620z and 2155z
QRNE TK I RT BAS E RCV DE RMGBK RM PT 5 6 W08 K II II
RMGB RWE 5620OE 67 4 G 7617 TP03 UTT TW E B RPT 562
E67164 77617 09039 = ARRMGB K NBOKQRUMD IEESLIZ
VVV RCV RCV RCV DE RMGB RMGB QSA?
ATC K VVV R RVI CV RCV TIE RMGB RMGB QSA? QTCK RMG
TI 844 JT9 9 2100 8 U4 = SML FOR AEJH45 RJE 73=
09181 99360 7NO056 E41998 12310 10160 40220 54 00
7TO200 810T O1 T2252 00180 20101 88000 80000 09015 = AR
RMGB K RMGB RPT 844 19 9 M100 844 K E RMGB RPTK E RMGB APT
0056 E E 41220 H4MO00 K RMGB RPT 0018 J 20101 K RMGB OK QNU
K GCVDE RMGB QRVK EEAIIH SIEIEM T GMGB NR 256 RPT
1 5 10 K E E RMGB NR 256 RPT 11 12 1EM K RMGBNR
56 RPT 22 32 K RMGBN N 256 RPT 22 32 K RMGB QSL 256 K
-
I caught all that too. They were apparently training some new radiomen as the timing was mostly 5 wpm or so, and spacing was all over the place, but decent sig levels.
-
yeah, it was pretty jumbled
-
de RME81 RME81 FOR RIW RIT RMP (groups)
8345 0316Z 15MAR20
VVV RIW RIW RIW de RME81 RME81 QSA? QTC K
(groups)
QSL 91912 919? K
RME81 OK QRU K
8345 0357Z 15MAR20
VVV RCV RCV RCV de RMGB RMGB QSA? QTC K
(two or more stas interfering here)
RMGB RPT 45
RMGB OK QRU K
8345 0603Z 15MAR20
RME81
8345 0613Z 15MAR20
VVV RIW RIW RIW de RMUW RMUW QSA?QTC K
FOR RJE73 =SML= (groups) AR RMUW K
8345 0617Z 15MAR20
VVV RCV RCV RCV de RMUW RMUW QSA? QTC K
8345 0617Z 15MAR20
VVV RIW RIW RIW de RMUW RMUW QSA? QTC K
FOR RJE73 RJH45 RJH74 =SML= (groups)
8345 0618Z 15MAR20
VVV RCV RCV RCV de RMGB RMGB QSA? QTC K
8345 0646Z 15MAR20
-
nice, did the date get scrambled?
-
Lol I need an editor.
-
All 8345
VVV RIT RIT RIT de RMGB RMGB QSA? QTC K
0211Z 11MAR20
VVV RIW RIW RIW de RMGB RMGB QSA? QTC K
0212Z 11MAR20
VVV RIT RIT RIT de RMGB RMGB QSA? QTC K
FOR RJH45 RJE73 RJH74 (groups)
0211Z 11MAR20
-
Think from now on only the unusual, plus any new calls heard, will be added to the thread on my part.
-
I know what you mean Josh. Last night was busy.
-
8345 kHz
Mar 28 between 0100z and 0900z
RCV RCV RCV DE RJS81 RJS81 QSA? QTCK
RIW RIW RIW DE RJS81 RJS81 QSA? QTCK RJS81 728 Q
RJS81 RJS81 OK Q RUK
RDS RCV RCV DE NMGB RMGB QSA? QTCK RMGB
Josh, UDXF has RJS81 as a possible PM-82 repair ship, do you agree?
-
RJS81 aka the "Gazolin", a PM-82 Amur Class Floating Workshop of the glorious Baltic Fleet.
https://www.youtube.com/watch?v=8hZugE_8W8k
bonus soviet navy fun;
https://www.youtube.com/watch?v=N4jQhnXrWbg
Send strong soviet signals, comrades!
-
Thanks Josh
-
Informatsia na Floating workshop, droog moy
http://russianships.info/eng/support/project_304.htm
Nice page on Russian Navy;
http://russianships.info/eng/today/
-
Our friend RSJ81 gave this as her position report on 8345 not long ago;
https://www.google.com/maps/place/37%C2%B018'00.0%22N+3%C2%B054'00.0%22E/@39.537677,-1.9447265,5z/data=!4m5!3m4!1s0x0:0x0!8m2!3d37.3!4d3.9?hl=eb
-
If using an app to decode stronk soviet signalskiis, it helps to get as close to the intent as possible, meaning no extra parsing added. Many cw decoder apps will try to add HAM prosigns to any sig because HAMs. And that is bad enough without the additional pita of cw being sent not in English, but Cyrillic. How many cw decoders, human or otherwise, can do Cyrillic cw? Wcode does and is the only one I know of right now.
So how to fix problem?
Is easy!
Use CW Decoder.
https://download.cnet.com/developer/wd6cnf/i-10119931
After installing this gem, click text on the menu bar at top of app, select spaces and select yes, then select space time of medium, Prosigns set to disable, and non-english to enabled.
Sadly there's no means to have time of intercept printed with the output in cw decoder.
https://www.youtube.com/watch?v=VWaQcKiAj_Q
-
Thanks Josh
-
RJS81 gave this as its posrep today;
https://www.google.lt/maps/place/43%C2%B054'00.0%22N+9%C2%B012'00.0%22E/@42.4580496,6.2117188,6z/data=!4m5!3m4!1s0x0:0x0!8m2!3d43.9!4d9.2?hl=en
-
Our friend RSJ81 has ventured forth into the big ocean;
https://www.google.lt/maps/place/45%C2%B007'00.0%22N+7%C2%B054'00.0%22W/@46.0470342,-16.6451171,4z/data=!4m5!3m4!1s0x0:0x0!8m2!3d45.1166667!4d-7.9?hl=en
-
He’s been busy lately
-
Today around 1220Z there was a few mins of high speed cw that was too weak to copy, afterwards a dasher that sent for 4 secs or so with a 25 sec interval. Sent till about 1500z or fadeout at that time.
https://voca.ro/o4IKl9BjCcY
Rig was IC-775 with 80Hz Audio Peak Filter enabled.
-
RJS81 gave wrong posrep on 10th April 8) , real position is here (the operator changed East for West coordination - it sometimes happens)
https://www.google.lt/maps/place/43%C2%B054'00.0%22N+9%C2%B012'00.0%22W/@43.1993034,-24.0535155,4z/data=!4m5!3m4!1s0x0:0x0!8m2!3d43.9!4d-9.2?hl=en
-
soviets bein tricky!
-
A lot of catches lately on
https://groups.io/g/UDXF/messages (https://groups.io/g/UDXF/messages)
about the Russian navy
-
According to our spies, the soviets are fixin to loft another asat test today, if they haven't already. One of the splash down areas is Barents Sea, the other the Laptev Sea. Any weird stuff going on might be part of the testing regimen, there was a carrier on for an hour or so earlier today. A unit was calling RMP (Navy HQ Kaliningrad) around 1000R, Romeo time being US eastern time.
That said, this url has no mention of any tests today;
http://russianforces.org/
-
Tony posted this catch and summary at his page here;
http://i56578-swl.blogspot.com/2020/06/50bd500-fsk-likely-cis-govmil.html
50Bd/500 FSK (likely CIS Gov/Mil)
Ran the linked audio file thru K500 to see what it said and it triggered the KG84C parser;
[2020-06-13 19:38:59] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:00]
[2020-06-13 19:39:00]
[2020-06-13 19:39:00] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:01]
[2020-06-13 19:39:01]
[2020-06-13 19:39:01] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:03]
[2020-06-13 19:39:03]
[2020-06-13 19:39:03] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:04]
[2020-06-13 19:39:04]
[2020-06-13 19:39:04] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:05]
[2020-06-13 19:39:05]
[2020-06-13 19:39:05] Detected KG-84C SYNC with 93% confidence
[2020-06-13 19:39:06]
[2020-06-13 19:39:06]
[2020-06-13 19:39:06] Detected KG-84C SYNC with 92% confidence
[2020-06-13 19:39:08]
[2020-06-13 19:39:08]
[2020-06-13 19:39:08] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:09]
[2020-06-13 19:39:09]
[2020-06-13 19:39:09] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:10]
[2020-06-13 19:39:10]
[2020-06-13 19:39:10] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:11]
[2020-06-13 19:39:11]
[2020-06-13 19:39:11] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:13]
[2020-06-13 19:39:13]
[2020-06-13 19:39:13] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:14]
[2020-06-13 19:39:14]
[2020-06-13 19:39:14] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:15]
[2020-06-13 19:39:15]
[2020-06-13 19:39:15] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:17]
[2020-06-13 19:39:17]
[2020-06-13 19:39:17] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:18]
[2020-06-13 19:39:18]
[2020-06-13 19:39:18] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:19]
[2020-06-13 19:39:19]
[2020-06-13 19:39:19] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:20]
[2020-06-13 19:39:20]
[2020-06-13 19:39:20] Detected KG-84C SYNC with 100% confidence
[2020-06-13 19:39:22]
[2020-06-13 19:39:22]
[2020-06-13 19:39:22] Detected KG-84C SYNC with 90% confidence
[2020-06-13 19:39:32] Initialization vectors: 4443CF0683C041C0 43C3C3C3C3C3C3C3
[2020-06-13 19:39:33] C3C3C3C3F0F0C3C3C3C3C3C3C3C3C3C3C3C3C3C3F0F0C3C3C3C3C3C3C3C3C3C3C3C3C3C3F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0FFFFFFFFFFFFFFFF
[2020-06-13 19:39:44] End of message (idle pattern)
Mebbe not cis nav but fun anyway.
-
Mebbe not cis nav
Considering Tony's catch came from Novosibirsk, Russia, which is "the second-farthest substantially populated city from the ocean"[1] ;D
[1]https://en.wikipedia.org/wiki/Novosibirsk#Location
-
VVV VVV RIT RIT RIT de RGB59 QTC? etc etc
8345 0316Z 02FEB21
RGB59 - new call logged, voice call MALBERT, of the Black Sea Fleet, iono what kinda ship it is, very stronk sovietskaya signalskiis at this QTH
-
12464 has featured some interesting simplex traffic between two stas around 2300z if anyone is still listening.
-
8)
-
VVV VVV RIT RIT RIT de RIS89 QTC? etc etc
12464 2300Z 05AUG21
New callsign, dunno what ship, also decoded as RIS589 on later xmissions, told RIT they had them at QSA3 signal level. Attempted contact with RIT several times until 0103Z the next day.
-
RME81 OK QRU K
8345 0800Z 21AUG21
caught end of lengthy tx from RME81
RME81 is cw call for RU Navy ship MB-119, voice callsign Ladnik, a Goryn Class 2200 ton Ocean Tug of Baltic Fleet
Apparently looks something like this;
https://c8.alamy.com/comp/PGBM37/aerial-port-side-view-of-the-russian-navy-pacific-fleet-goryn-class-ocean-going-tug-mb-105-PGBM37.jpg
In honor of new Soviet callsign rx'd, Soviet navy song!
https://www.youtube.com/watch?v=CNEnvhNw7AM
strong soviet signals to all comrades
-
12464 1733Z 30AUG21
Lots of weak/unreadable cw for a time, then settles into a 4 second dash every 25 secs till los an hour or more later, think last time this dash every 25 secs took place they were testing a missile so mebbe another test launch.
-
de RGB59 QTC? etc etc
8345 0255Z/0600Z 10OCT21
RJI58 - new call logged, voice call BRILLIANT, Rescue Tug Spasatel Vasily Bekh, Project 22870 Rescue Tug of the Black Sea Fleet, a lovely lass;
https://www.kchf.ru/eng/photos/photo_rescue/en_sb739_01.htm
And in honor of new callsign
https://www.youtube.com/watch?v=EjZtn_RLdqU
stronk soviet signals to all camarads!
-
7632kHz cw RJS RJS QSA? K 1406z 25 Nov /21
-
7632kHz cw RJS 1421z 26 Nov /21
-
7632kHz cw RJS 1440z 28 Nov /21
-
12464 1733Z 30AUG21
Lots of weak/unreadable cw for a time, then settles into a 4 second dash every 25 secs till los an hour or more later, think last time this dash every 25 secs took place they were testing a missile so mebbe another test launch.
same as above ongoing @ 1729Z 10DEC21
-
6916 T600 36/50 FSK 2319Z 14DEC21
Multiple encrypted messages, weak -118dBm but stable sig level.
hex output;
21 07 07 08 02 00 02 0B 10 1C 19 0D 1D 08 _00 0E _____05 _06 _1F _05 00 _11 12 1
F 10 0E 19 08 04 1E 22 03 05 __
[END OF MESSAGE]
11 04 01 06 1D 1C 10 0F 00 18 1C 16 08 _04 1C 02 __1A 07 07 _07 _04 _____0E 0A 0
0 1E 16 17 10 0A 04 07 10 __17 _09 ____08 08 ___1C 07 22 1D 1F 0D 05 01 11 12 1F
______10 19 _1E __12 _0A 15 0E 0A 0F 0C 1E 1C 03 19 0A _01 ___00 ___13 _0A 03 2
0 _01 1C _0D 1B 02 00 1F 01 14 14 0B _22 ____03 20 14 1F 21 00 _16 08 _0C ___13
1A 16 1A _____0C 17 0B 0E 05 1D 1B 21 07 ________0C 08 0E 22 0A 10 09 _0F _1F 04
18 0C 18 0E 1A 1D 04 1E 05 02 0C 08 01 21 _0B 0B ___16 22 18 09 __09 _01 ___11
19 08 0F 0B 0C 14 1E 08 11 0D 0E _08 __01 _13 __04 01 ___0E _0D 14 00 1C 1D 0E 1
1 18 07 08 05 _01 __0A ____21 _0F 05 __1C 07 08 00 16 1D 05 1B 21 1E 21 18 19 0B
17 10 _21 1E 14 01 _0F 0F _0C ______1A _0E 0D 1E 21 14 10 0E 08 0B 21 17 02 02
0B 17 0D 07 1E 0D 0B _09 06 1A _16 0A 22 _0F __1E 1B _____10 05 04 17 18 1D 1A 1
9 1E 04 16 09 0F 0D ___17 __22 _0C __15 __05 05 17 1C 0F 1E 11 04 1F _07 00 _05
________03 0F 1E 0E 17 05 12 0B 08 05 0A 1D 01 04 0F 1A _03 _____10 _09 ___17 1B
01 1B 0C 03 12 04 _____0B 04 ___1F _1C 01 20 1A 07 _03 1D 02 09 08 0A 22 0A 06
08 07 ___03 ______0C _11 11 16 0E 1A 0F 0A 14 0D 14 03 16 01 0E 05 11 1F _00 __2
2 __1F _1F __10 20 __22 09 09
https://www.sigidwiki.com/wiki/CIS-36-50
http://www.wavecom.ch/content/ext/DecoderOnlineHelp/default.htm#!worddocuments/cis3650.htm
-
6916 T600 36/50 FSK 2319Z 14DEC21
Multiple encrypted messages, weak -118dBm but stable sig level.
hex output;
21 07 07 08 02 00 02 0B 10 1C 19 0D 1D 08 _00 0E _____05 _06 _1F _05 00 _11 12 1
F 10 0E 19 08 04 1E 22 03 05 __
[END OF MESSAGE]
11 04 01 06 1D 1C 10 0F 00 18 1C 16 08 _04 1C 02 __1A 07 07 _07 _04 _____0E 0A 0
0 1E 16 17 10 0A 04 07 10 __17 _09 ____08 08 ___1C 07 22 1D 1F 0D 05 01 11 12 1F
______10 19 _1E __12 _0A 15 0E 0A 0F 0C 1E 1C 03 19 0A _01 ___00 ___13 _0A 03 2
0 _01 1C _0D 1B 02 00 1F 01 14 14 0B _22 ____03 20 14 1F 21 00 _16 08 _0C ___13
1A 16 1A _____0C 17 0B 0E 05 1D 1B 21 07 ________0C 08 0E 22 0A 10 09 _0F _1F 04
18 0C 18 0E 1A 1D 04 1E 05 02 0C 08 01 21 _0B 0B ___16 22 18 09 __09 _01 ___11
19 08 0F 0B 0C 14 1E 08 11 0D 0E _08 __01 _13 __04 01 ___0E _0D 14 00 1C 1D 0E 1
1 18 07 08 05 _01 __0A ____21 _0F 05 __1C 07 08 00 16 1D 05 1B 21 1E 21 18 19 0B
17 10 _21 1E 14 01 _0F 0F _0C ______1A _0E 0D 1E 21 14 10 0E 08 0B 21 17 02 02
0B 17 0D 07 1E 0D 0B _09 06 1A _16 0A 22 _0F __1E 1B _____10 05 04 17 18 1D 1A 1
9 1E 04 16 09 0F 0D ___17 __22 _0C __15 __05 05 17 1C 0F 1E 11 04 1F _07 00 _05
________03 0F 1E 0E 17 05 12 0B 08 05 0A 1D 01 04 0F 1A _03 _____10 _09 ___17 1B
01 1B 0C 03 12 04 _____0B 04 ___1F _1C 01 20 1A 07 _03 1D 02 09 08 0A 22 0A 06
08 07 ___03 ______0C _11 11 16 0E 1A 0F 0A 14 0D 14 03 16 01 0E 05 11 1F _00 __2
2 __1F _1F __10 20 __22 09 09
https://www.sigidwiki.com/wiki/CIS-36-50
http://www.wavecom.ch/content/ext/DecoderOnlineHelp/default.htm#!worddocuments/cis3650.htm
This hex output 50/200 ? via Rivet?
6916kHz a new CIS-36-50 freq? Boender reports 6916 on 6 Aug /20 as FSK 200/1000 Russian diplo/intel
-
6916 T600 36/50 FSK 2319Z 14DEC21
Multiple encrypted messages, weak -118dBm but stable sig level.
hex output;
21 07 07 08 02 00 02 0B 10 1C 19 0D 1D 08 _00 0E _____05 _06 _1F _05 00 _11 12 1
F 10 0E 19 08 04 1E 22 03 05 __
[END OF MESSAGE]
11 04 01 06 1D 1C 10 0F 00 18 1C 16 08 _04 1C 02 __1A 07 07 _07 _04 _____0E 0A 0
0 1E 16 17 10 0A 04 07 10 __17 _09 ____08 08 ___1C 07 22 1D 1F 0D 05 01 11 12 1F
______10 19 _1E __12 _0A 15 0E 0A 0F 0C 1E 1C 03 19 0A _01 ___00 ___13 _0A 03 2
0 _01 1C _0D 1B 02 00 1F 01 14 14 0B _22 ____03 20 14 1F 21 00 _16 08 _0C ___13
1A 16 1A _____0C 17 0B 0E 05 1D 1B 21 07 ________0C 08 0E 22 0A 10 09 _0F _1F 04
18 0C 18 0E 1A 1D 04 1E 05 02 0C 08 01 21 _0B 0B ___16 22 18 09 __09 _01 ___11
19 08 0F 0B 0C 14 1E 08 11 0D 0E _08 __01 _13 __04 01 ___0E _0D 14 00 1C 1D 0E 1
1 18 07 08 05 _01 __0A ____21 _0F 05 __1C 07 08 00 16 1D 05 1B 21 1E 21 18 19 0B
17 10 _21 1E 14 01 _0F 0F _0C ______1A _0E 0D 1E 21 14 10 0E 08 0B 21 17 02 02
0B 17 0D 07 1E 0D 0B _09 06 1A _16 0A 22 _0F __1E 1B _____10 05 04 17 18 1D 1A 1
9 1E 04 16 09 0F 0D ___17 __22 _0C __15 __05 05 17 1C 0F 1E 11 04 1F _07 00 _05
________03 0F 1E 0E 17 05 12 0B 08 05 0A 1D 01 04 0F 1A _03 _____10 _09 ___17 1B
01 1B 0C 03 12 04 _____0B 04 ___1F _1C 01 20 1A 07 _03 1D 02 09 08 0A 22 0A 06
08 07 ___03 ______0C _11 11 16 0E 1A 0F 0A 14 0D 14 03 16 01 0E 05 11 1F _00 __2
2 __1F _1F __10 20 __22 09 09
https://www.sigidwiki.com/wiki/CIS-36-50
http://www.wavecom.ch/content/ext/DecoderOnlineHelp/default.htm#!worddocuments/cis3650.htm
This hex output 50/200 ? via Rivet?
6916kHz a new CIS-36-50 freq? Boender reports 6916 on 6 Aug /20 as FSK 200/1000 Russian diplo/intel
Yes, wcode, next time will use raw decode rather than hex.
-
6912 cf T600 36/50 FSK 126Z 16DEC21
0038 0038 001C 001C 000E 000E 0007 0043 0063 0071 0071 0038 0038 001C 001E 000E
0007 0054 0077
[END OF MESSAGE]
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 0060 001E 002C 005C
003D 0009 0054 002A 0075 003A 0055 0007 000B 004C 0058 000E 0058 0034 0013 0032
0016 0013 004C 0034 0061 0052 0015 0045 0026 000D 000D 0062 0019 0070 000D 002C
0045 0029 0016 0034 0038 0032 0043 0032 0070 0038 0013 000B 0064 0052 000E 0014
000E 0062 0013 0070 003E 000B 000F 0065 003C 0056 005D 0042 0054 0046 0034 0016
0045 000E 0077 0077
[END OF MESSAGE]
001A 0025 0025 000D 0029 0025 002C 0034 002A 0038 001C 000C 000B 0009 0029 0035
005C 0035 002B 0038 001C 004C 0003 0031 0013 0034 001A 0054 0038 0033 002A 0058
002A 0015 0054 0046 002C 0062 0043 0052 0038 0064 0015 0013 0070 0058 0070 0046
0013 0034 0019 0052 000E 0043 006A 006C 0039 0052 0001 0001 005F 0064 0064 0023
002A 0031 0015 001D 0034 0016 0037 006E 0058 0063 0047 0072 0077 0077
[END OF MESSAGE]
wcode raw output
-
T-600 599 8345 Washington D.C. HEAVY volume of traffic. 0830z.
-
Rivet T-600 (CIS36-50) decoder;
Baudot (various speeds) : Used by amateurs , weather stations and other users.
CCIR493-4 : A HF selective calling mode
CIS36-50 (50 baud only currently) : Used by the Russian Navy.
CROWD36 : Used for Russian diplomatic and intelligence messages
FSK200/500 : Used for Russian diplomatic and intelligence messages
FSK200/1000 : Used for Russian diplomatic and intelligence messages
FSK (raw) : For advanced users to investigate unknown FSK modes
GW FSK (100 baud) : A commercial ship to shore data system.
XPA (10 and 20 baud) : Believed used for Russian intelligence messages.
XPA2 : Believed used for Russian intelligence messages.
https://github.com/IanWraith/Rivet
http://www.signalshed.com/rivet/
-
8345 0100Z 29DEC21
VVV RCV RCV RCV de RJI48 and into wx and posrep
RJI48, voice call "BRILLIANT" hull SB-739, a Project 22870 Rescue Tug of Black Sea Fleet
RCV is Black Sea Fleet HQ
And some pics of the lovely lass;
https://www.kchf.ru/eng/ship/rescue/sb739.htm
in honor of suspected new soviet call sign....
https://www.youtube.com/watch?v=j2ER6VTaAyk
song seems to dis northern and black sea fleet duty
stronk soviet signala to all kamarad
-
12464 1733Z 30AUG21
Lots of weak/unreadable cw for a time, then settles into a 4 second dash every 25 secs till los an hour or more later, think last time this dash every 25 secs took place they were testing a missile so mebbe another test launch.
Something similar is taking place right now 1858Z 12DEC2022
-
T-600 599 8345 Washington D.C. HEAVY volume of traffic. 0830z.
I've only seen them run it on 8345 once and that was only heard by the most sensitive rig here, nice catch.
-
8599kHz cw RJS de RGR78 1410z 18 Feb /22
-
4649.5 USB . RUS mil net NAVY. Black see fleet.
C/s POEMA, GARPUNER , 1th, 2th,6th. Coordinates / course / knots .
-
According to this doc, the command net structure I considered to be via hf might be a geostationary satcomms system rather than terrestrial;
https://webcache.googleusercontent.com/search?q=cache:60Rdrda5G70J:https://en.topwar.ru/36729-voennye-sistemy-sputnikovoy-svyazi.html+&cd=13&hl=en&ct=clnk&gl=ca&client=ubuntu
Similar to our fleetsats, afsatcom, and follow on geos. The ruskiis also have leo sats that perform store and forward messaging
More info on ruskii satskiis;
https://twitter.com/coastal8049/status/1498462497463934976
don't get into trouble, you know how we do not encourage any radio signals that violate regulations and so on.
-
12464 1733Z 30AUG21
Lots of weak/unreadable cw for a time, then settles into a 4 second dash every 25 secs till los an hour or more later, think last time this dash every 25 secs took place they were testing a missile so mebbe another test launch.
same as above ongoing @ 1600Z 15SEP22
-
"Oh no! Another hypersonic missile hit Motherland! I hope it not hit Kremlin. Let us make like Battleship Potemkin and scram!"
-
They're possibly testing their humanitarian nuclear armed and nuclear powered cruise missile, Burevestnik, you know the one that covers the ground it flies over with, oh, I dunno, cobalt 60 or whatever. Their track record's not so good right now as a previous test blew up on the launch pad making geiger counters in the eu angry.
https://en.wikipedia.org/wiki/9M730_Burevestnik
Or mebbe one of these as they can be launched by naval aircraft;
https://en.wikipedia.org/wiki/Kh-47M2_Kinzhal
Ukraine found one intact, it likely ended up at some cia lab along with all the other cool doodads Russia leaves behind.
-
Bob Lazar and his Space Brothers have it at Area 51.
-
You mean the Bob Lazar who is with the Galactic Space Police Brotherhood?!?
-
A kind soul sent me a recording of a 22m fsk interloper. The signal is CIS 36/50 in this case, with hand sent cw opchat (operator chatter where the radiomen coordinate the setup and takedown of the link in hand sent fsk cw) interspersed with messages.
https://www.sigidwiki.com/wiki/CIS-36-50
The recipient is RDL, or all strategic ie nuclear forces of the Russian federation. This signal is simulkeyed from vlf to vhf on many different freqs so a unit can find the best propagating signal or signals to decode. They don't care where they set up a link, could be HAM bands, could be ISM, stronk soviet signals to all!
What they are doing with these simulkeyed transmissions is fleet broadcast, where there is a constant message stream from HQ to afloat units. Their land based nukes can also tune in. Just like our subs have a buoy packed with antennae and electronics tethered to the sub that cruises along just under the surface where it can pick up our fleet broadcast (USN/NATO uses fsk 50Bd) that keep a constant watch on the broadcast, so does Russia. There are two distinct simulkey nets used by Russia where kremlin directly communicates with afloat units, subverting/bypassing lower commands such as Navy HQ. There are also multiple Russian Navy HQ broadcasts on hf too, from each respective HQ; Vladivistok, Murmansk, Astrakhan, Kaliningrad, etc.
I have a few ideas as to why there are two national command/Kremlin simulkey nets. One is reliability, if one net goes down they still have another at least for a while. Perhaps one net is Russian Navy HQ while the other is direct Kremlin link. Perhaps one is for ssns while the other for ssns. It's fun to consider solutions to the problem.
One Ping Only
-
13558 kHz, RDL has been very active today at 1215z and afterwards with RTTY and FSK CW "RDL RDL" followed by six 5-number group and on/off short RTTY transmissions.
Dave
-
13:10 UTC 26 MAR 2023 - Good readable on 13558 kHz at an S6 with RTTY; Mark: 1275 Shift: 200.
RSPduo | Barker & Williamson T2FD & Wellbrook loop antennae
-
Nice logs gents, 13558 Kaliningrad is just now (3303Z 31MAR23) finishing opchat fsk cw and going into T600 traffic.
And a decoder of sorts for various modes;
https://github.com/IanWraith/Rivet