Sunday 28 June 2015

Russian Navy Kaliningrad 8459.0 (more)

Last night at 1843 I tuned again to 8459.0khz USB and cw signals were present. This time I didn't record it, but fed the signal directly into MULTIPSK using the QRP decoding function and switched from the big signals with white noise of the outdoor vertical to the quiet signals with no noise of the indoor loop. The results were much, much better using the indoor loop: despite the signal really dropping very low at times, the QRP function on MULTIPSK had no problem decoding. You would never believe such a low signal level could result in such good decoding - it had to be seen to be believed.

In fact, MULTIPSK has always proven to be exceptionally good at handling low quality and low level signals, consistently beating the competition hands-down. And having such an enormous array of modes makes it a very good value and high-quality package.

Anyway, back to the Russian Navy. After the familiar "tire" and "tok" words and numbers I was familiar with from the other night, we got "peterburg" and an "AR" at the end of the message. The next message began:

"REO REO de RMP RMP QTC ........"

Here is the screenshot of this interesting ID part of the message:



Have a look at Tony's PLANESANDSTUFF BLOG blog and his Russian callsign list and you will see this is a weather warning for the Baltic Sea (REO) from Baltic Fleet HQ, Kaliningrad (RMP). I am not too sure about the QTC. Perhaps it is "message follows", "we have a message for you" from what I see on Google.

 I entered the word "RABOTY" into a Latin - Cyrllic alphabet online site and then copied the Russian characters to Google language translator and it means "WORK". It is time-consuming but fascinating to a language enthusiast like myself to decipher the text in this way.

My next challenge is to move away from this mostly broadcast oriented transmission to decoding CW to and from actual ships.



5 comments:

  1. Hello, I copied REO de RMP today on 5292KHZ at approximately 20:00UTC. I also used MULTIPSK for decoding. I am located in Pennsylvania, callsign N3YQA. Here was the traffic that I copied: REO REO DE RMP RMP QTC 827 120 15 2015 82= WSEM SUDAM DEJSTWUÜQIE PRIP KALININGRAD NA 16000MIST3555SSS2855 GOD 86 234 2017 GOS 39 146 232 201GSS 2957 129 249 270 277 349 375 390 391 392 393 394 409 425 429 2017SSS4 5 21 23 34 49 66 67 68 69 70 71 DEJSTWUÜQIE PRIP PETERBURG NA 160095IISEé555SSS2855SSS15£55558 418 2015DSS12 150 158 162 175 189 198 555554 195 216 2 7 84 291 97 306 10 26 30 31 3436 361 363 36367 370 374 88 395 396 00 403 404 209 SS3 16 17 19 24 226 9 33 34 6 37 40 41 2 AR

    ReplyDelete
    Replies
    1. Hi Scott, it's fascinating stuff isn't it monitoring Russian military activity and so cool when you get some call signs and text you can understand. I have been monitoring the Russian single letter Beacons recently. Thanks for leaving the comments and keep me up to date on any other interesting catches you get. I've not written in my blog for ages but I'm always on the radio listening to something or other utility oriented!

      Delete
  2. AWESOME Scott. There is something really cool about copying the Russian Military like this. And even more amazing for you being so much further away. Great!

    ReplyDelete
  3. received reo de rmp qtc (conts in tfc) on 5180khz between 2021L to 2037L UK time. mode abm1a qsa1/2 from here in Gloucester UK

    ReplyDelete
  4. Hi, I just listened to it on 8417.6 Khz. Here is the transcript with CwGet: "reo reo de rmp rmp qtc 567 46 27 1045 567 = 11111 78355 26600 22686 43*** 966408 00523 12523 81176 54520 25738 06561 843** 79612 93865 7702l* 77165 90984 **426 69318 80232 90422 52052 18114 91711 24099 24576 81422 85218 61612 09618 09232 38360 77676 12798 62851 87414 86655 67078 87631 59818 77789 91251 36429 31372 27045" The * symbol fills in when the transmission was unclear.

    ReplyDelete