We seek to understand and document all radio transmissions, legal and otherwise, as part of the radio listening hobby. We do not encourage any radio operations contrary to regulations. Always consult with the appropriate authorities if you have questions concerning what is permissable in your locale.

Author Topic: Russian MX beacons log.  (Read 6869 times)

Offline Looking-Glass

  • Hero Member
  • *****
  • Posts: 596
    • View Profile
Russian MX beacons log.
« on: July 19, 2017, 0856 UTC »
The lower bands have been more productive than frequencies above 13MHz or so, as per normal, the hours of darkness yield the best results here in Australia:

July 2017 so far:

1646z  5.154.5MHz  CW  "M" Magadan, Sea of Okhotsk, Far East 419 report.
1449z  5.621.0MHz  CW  "V"  Khiva, Xorazm, Uzbekistan, unpublished frequency so maybe not Khiva? 319 report.

1644z  7.508.1MHz  CW  "A" Astrakhan,Volga River, 539 report.
1646z  7.508.9MHz  CW  "S" Severomorsk, Kola Bay, Murmansk region, 529 report.

1557z  8.495.1MHz  CW  "A" Astrakhan, Volga River 589 report.
1708z  8.495.2MHz  CW  "L" St Petersburg, Baltic Sea & Neva River 519 report.
1037z  8.495.3MHz  CW  "F" Vladisvostok, Far East, Sea of Japan 529 report.
1620z  8.495.3MHz  CW  "K" Petropavlovsk, Kamchatskiy, Kamchathka, Bering Sea 319 report.
1623z  8.504.0MHz  CW  "K" continuous until 1640z then gone, probably not Petropavlovsk but fist, spacing and transmission phase identical. (18th July 2017).
1040z  8.504.0MHz  CW  "K K K K K A K K K K K A K K K K K A" etc, Petropavlovsk also on air 8.495.3MHz 539 report, mystery, also letter "A" after every five "K" letters sent. 419 report. (21 July 2017)

0909z  10.871.7MHz  CW  "D" Sevastapol, Black Sea 429 report.

0856z  13.528.4MHz  CW  "M" Magadan, Sea of Okhotsk, Far East 539 report.

Both Magadan and Astrakhan are always strong here, whether it's the propagation or the transmitter power? Not a lot heard from Khiva of recent.

The 1040z observation of "K" five times then "A" and so on at 8.504MHz is probably Petropavlovsk as it was on the same time on 8.495.3MHz, they both faded out around the same time and similar "fist" on the transmission, any one know what the "A" designates?  ???

Former USSR channel marker/beacon stations:

B  Arkhangelsk
C  Moscow
F  Gdynia (Poland)
H  Unknown
O  Moscow
P  Kaliningrad
R  Izhevsk
S  Arkhangelsk
T  Unknown
U  Kholmsk
W Havana (Cuba)
X  Prague (Czech)

All of the above have virtually closed down since the demise of the former USSR, or maybe they are just "sleeping"? 8)
« Last Edit: October 13, 2018, 2220 UTC by Looking-Glass »
Hermitage Flat, NSW.

Grid Square:  QF56dm.

Yaesu FT-2000D, ICOM IC-736 HF/50MHz, ICOM IC R75 & Tecsun S-2000 to 450 feet of wire, and a multi band vertical of dubious reliability.

Offline Looking-Glass

  • Hero Member
  • *****
  • Posts: 596
    • View Profile
Re: Russian MX beacons log.
« Reply #1 on: July 31, 2017, 1059 UTC »
Mystery of Petropavlovsk "K" with the added "A" after five lots of "K" sent, defective transmitter.  Information in separate posting in the Beacon section... :D
Hermitage Flat, NSW.

Grid Square:  QF56dm.

Yaesu FT-2000D, ICOM IC-736 HF/50MHz, ICOM IC R75 & Tecsun S-2000 to 450 feet of wire, and a multi band vertical of dubious reliability.

Offline sat_dxer

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
    • Email
Re: Russian MX beacons log.
« Reply #2 on: August 07, 2017, 2003 UTC »
"M" fade in on 13528.4kHz at 1900z 7 Aug 2017
Most times & frequencies posted are only an approximation.
Due to adulteration of the E.N.I.G.M.A. "designators" by others and not a match in the Conet Project they are never used.
-30-

Offline sat_dxer

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
    • Email
Re: Russian MX beacons log.
« Reply #3 on: September 27, 2017, 1530 UTC »
8495.3  "K" w/what sounds like TEEEEE and other mixed up cw from 1520z 27 Sept 2017
« Last Edit: September 27, 2017, 1533 UTC by sat_dxer »
Most times & frequencies posted are only an approximation.
Due to adulteration of the E.N.I.G.M.A. "designators" by others and not a match in the Conet Project they are never used.
-30-

Offline sat_dxer

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
    • Email
Re: Russian MX beacons log.
« Reply #4 on: September 29, 2017, 2341 UTC »
13528.4kHz  CW  "M"
13528.3kHz  CW  "K"
from 2000z 29 Sept 2017
13528.2kHz  CW  "F"
fade in 0048z 30 Sept 2017
« Last Edit: September 30, 2017, 0051 UTC by sat_dxer »
Most times & frequencies posted are only an approximation.
Due to adulteration of the E.N.I.G.M.A. "designators" by others and not a match in the Conet Project they are never used.
-30-

Offline sat_dxer

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
    • Email
Re: Russian MX beacons log.
« Reply #5 on: October 04, 2017, 0207 UTC »
16332.4kHz  CW  "M"
fade in 0205z 4 Oct 2017
Most times & frequencies posted are only an approximation.
Due to adulteration of the E.N.I.G.M.A. "designators" by others and not a match in the Conet Project they are never used.
-30-

Offline sat_dxer

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
    • Email
Re: Russian MX beacons log.
« Reply #6 on: October 04, 2017, 2310 UTC »
16332.4kHz  CW  "M"
fade in 2300z 4 Oct 2017
with occasional drops to what sounds like random pulse noise...

16332.2kHz  CW  "F"
weaker fade in @2335z 4 Oct 2017
« Last Edit: October 04, 2017, 2337 UTC by sat_dxer »
Most times & frequencies posted are only an approximation.
Due to adulteration of the E.N.I.G.M.A. "designators" by others and not a match in the Conet Project they are never used.
-30-

Offline Looking-Glass

  • Hero Member
  • *****
  • Posts: 596
    • View Profile
Re: Russian MX beacons log.
« Reply #7 on: October 06, 2017, 2138 UTC »
This morning I heard "I" on 5.154.8MHz CW in the period 1500-1630z.

One of the unidentified beacons/markers that appear out of nowhere from time to time, hasn't been heard for over three years this one.

Location not known, but presumed to be a Russian single letter beacon or marker, or Russian army rather than naval.

"I" was last heard in Europe on 3.814.8MHz CW and 12.149.5MHz CW.

Meanwhile on 8.459MHz CW "A" Astrakhan and "K" Petropavlovsk were both in for hours with Astrakhan the stronger peaking 579 report.
« Last Edit: October 06, 2017, 2142 UTC by Looking-Glass »
Hermitage Flat, NSW.

Grid Square:  QF56dm.

Yaesu FT-2000D, ICOM IC-736 HF/50MHz, ICOM IC R75 & Tecsun S-2000 to 450 feet of wire, and a multi band vertical of dubious reliability.

Offline sat_dxer

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
    • Email
Re: Russian MX beacons log.
« Reply #8 on: October 19, 2017, 0011 UTC »
16332.4kHz  CW  "M"

from 0000z 19 Oct 2017

16332.2kHz  CW  "F"
weaker fade in from 0035z 19 Oct 2017
« Last Edit: October 19, 2017, 0041 UTC by sat_dxer »
Most times & frequencies posted are only an approximation.
Due to adulteration of the E.N.I.G.M.A. "designators" by others and not a match in the Conet Project they are never used.
-30-

Offline SV1XV

  • Full Member
  • ***
  • Posts: 121
    • View Profile
    • SV1XV blog
Re: Russian MX beacons log.
« Reply #9 on: October 21, 2017, 1458 UTC »
5153.7 kHz  CW "D"
5156.8 kHz  CW  "F"   

around 03:15 UTC, 21 October 2017

My first of F on 5 MHz, it operates a couple of kHz higher than the rest of the cluster.


Offline SV1XV

  • Full Member
  • ***
  • Posts: 121
    • View Profile
    • SV1XV blog
Re: Russian MX beacons log.
« Reply #10 on: October 21, 2017, 2014 UTC »
5156.8 kHz  CW  "F"   
Tonight at 20:00 UTC, the beacon on 5156.8 sends again "L", as usual.

Offline Skywave

  • Newbie
  • *
  • Posts: 6
    • View Profile
Re: Russian MX beacons log.
« Reply #11 on: October 23, 2017, 2155 UTC »
5156.8 kHz - 2151z - drowned by signal that appears to be a jammer operating in Western Europe. Jammer sound heard over very large geographic area and on completely different types of receiver and aerial. Beacon occasionally breaks through loud and clear.

Jammer nearly continuous but with periodic break in transmission approximately every 14 seconds for 1 second.
Eton Satellit Grundig Edition (003 Firmware) || 40 m Longwire where specified || UK

Offline sat_dxer

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
    • Email
Re: Russian MX beacons log.
« Reply #12 on: October 31, 2017, 2303 UTC »
16332.4kHz  CW  "M"
fade in 2302z 31 Oct 2017
Most times & frequencies posted are only an approximation.
Due to adulteration of the E.N.I.G.M.A. "designators" by others and not a match in the Conet Project they are never used.
-30-

Offline sat_dxer

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
    • Email
Re: Russian MX beacons log.
« Reply #13 on: November 03, 2017, 2028 UTC »
13528.2kHz  CW  "F"
fade in 2025z 3 Nov 2017
--------------
16331.9kHz  CW  "S"
fade in 2045z 3 Nov 2017
---------------
16332.4kHz  CW  "M"
fade in 2320z 3 Nov 2017
« Last Edit: November 03, 2017, 2321 UTC by sat_dxer »
Most times & frequencies posted are only an approximation.
Due to adulteration of the E.N.I.G.M.A. "designators" by others and not a match in the Conet Project they are never used.
-30-

Offline Looking-Glass

  • Hero Member
  • *****
  • Posts: 596
    • View Profile
Re: Russian MX beacons log.
« Reply #14 on: November 04, 2017, 2204 UTC »
Late last night I heard "T" on 8.495.0MHz CW peaking 559, a new one, it was last heard on 6.934MHz CW a few years back, location unknown.

At first I thought it was one of the regulars with a miss key fault but also heard "A" Astrakhan at 1146z, "M" Magadan at 1136z, and "K" Petyropavlovsk at 1106z all working OK.

Every now and again a mystery unlisted one appears... :D

Hermitage Flat, NSW.

Grid Square:  QF56dm.

Yaesu FT-2000D, ICOM IC-736 HF/50MHz, ICOM IC R75 & Tecsun S-2000 to 450 feet of wire, and a multi band vertical of dubious reliability.