May 2004
Articles, newsreports and Items of interest :enigma2000-owner@yahoogroups.com
Morse stations | Voice stations | Oddities | Polytones
Numbers predictions | Non numbers | Propagation Indicator
How random is random ? | The Czechoslovakian government in exile - WWII
News Items | Web sites | Requests | Stop press | Contribution deadlines
Index | E2K NL Home
The CW team welcomes both LW & CWanon to its’ ranks, and appreciates their input and hard work.
As part of an ongoing re-evaluation by the E2K team of the CW scene your attention is drawn to the changes made to M03, which will be published in the next issue of the ENIGMA Control List, and included in this issue of the Newsletter for your information, see entry.
M93 is assigned, see entry.
Strange French Mil, Keith in Kent (KoK) was surprised to hear a FAV22 to include the word “Mephistopheles” in the chit chat after a coded TX !!!
Tue Mar 16th, 16.03z, 4139kHz, CW
This is a very strange TX, never heard previously.
aa 2 = 44749 65359
aa 2 = 55463 55838
aa 2 = t7788 77752
aa 2 = 41548 77566
aa 2 = 26492 87826
aa 2 = 4734t 656t4
aa 2 = 41214 91t6t
aa 2 = 9318t 17123
aa 2 = 92376 85254
aa 2 = 6256t 55t62
aa 2 = 46517 393t3
aa 2 = 354t6 39t18
aa 2 = 77428 76994
aa 2 = t81t7 55771
aa 2 = 7t952 83413
aa 2 = 572~2 68477
aa 2 = 73t83 45517
aa 2 = 19t87 25995
aa 2 = 15673 52124
aa 2 = 15731 634t3
aa 2 = tt811 71tt7
aa 2 = 23944 t9475
aa 2 = 75631 62959
aa 2 = 86t54 47336
aa 2 = 64944 25421
aa 2 = tt354 94325
aa 2 = 65444 35264
aa 2 = 8819t t1838
aa 2 = 1225t 64899
aa 2 = 5895t 83638
aa 2 = 3t973 147t5
aa 2 = 65398 25451
aa 2 = 79t21 66179
aa 2 = 32521 62824
aa 2 = 425t1 49157
aa 2 = 71812 69731
aa 2 = 89175 2t424
aa 2 = t6731 t4544
aa 2 = t5tt3 7tt22
aa 2 = 4t941 89843
aa 2 = t4315 38548
aa 2 = 64855 65t68
aa 2 = 61572 5111
aa 2 = 44199 47t8t
aa 2 = 4t472 6t721
aa 2 = 39186 185tt
aa 2 = 68t14 186t6
aa
aa 2 = 71896 7t771
aa 2 = 97122 t6322
aa 2 = 91247 82362
aa 2 = 89491 65872
aa 2 = 14346 22993
aa 2 = 3771t 15t72
aa 2 = 8t1t7 t59t2
aa 2 = 1t152 25254
aa 2 = 7972t 22742
aa 2 = 93812 65482
aa 2 = 58943 21637
aa 2 = t3583 t4942
aa 2 = 87551 8tt48
aa 2 = 7677t 85264
aa
aa 2 = 75845 2t588
aa 2 = 62691 63589
aa 2 = 97t95 38821
aa 2 = 14574 53894
aa 2 = 27786 31127
aa 2 = 11242 31136
aa 2 = 66282 t5619
aa 2 = 4t84t 15131
aa 2 = 14239 85565
aa 2 = 99232 11755
aa 2 = 88879 516tt
aa 2 = 27765
aa 2 =
nr ?
aa 2 = 11242
aa 2 = 81543 27tt8
aa 2 = 53779 6t868
aa 2 = 36195 33188
aa
aa 2 = 4t6t5 41387
aa 2 = 28776 55299
aa 2 = 7572t 26257
aa 2 = 48761 t6279
aa 2 = 21639 5t312
aa 2 = 119t7 18865
aa 2 = 68637 7538t
aa 2 = 52778 75t44
aa 2 = 65t3t t52t7
aa 2 = 575t8 2275t
c
aa
Igor B would appreciate any other log details if heard.
[possibly part of the M89 group, IB investigating. Ed]
| Mar 23rd | 07.00z | 16663kHz | cut 4f Clg “v bjcc bjcc bjcc de 3sa 3sa msg nr 4911/041” x 3 |
| Mar 24th | 01.05z | 16664kHz | cut, 4f Clg “ v bjcc bjcc bjcc de 3sa 3sa msg nr 8773/035” x 8 ck 21 0324 0355 = t6du 777t 5t73 5n33 5u66 7u6a a464 tu7a 3a6a 5dau 3uau 47n3 a5ua ntd3 7au4 ad44 ndt3 45u4 a6d4 na4d na4d. |
| Mar 30th | 00.36z | 5679kHz | CW, clg “vvv mwh mwh mwh de raw qru” R2 “t63 t63 SK SK” |
| Apl 14th | 06.11z | 9403kHz | CW, clg “vvv 67gh 67gh 67gh” (R) “id id nr 2tl 1413 = 67gv/kmn8” x 2, iii iii |
| Sun Mar 14th | 14.03z | 12144kHz | inside 25 Metre BC band, strong CW sending 4f gps using short zero, ended “ = 826 RPT AL QLN AR” |
| Tue Apl 20th | 18.10z in prog | 5474kHz | ending “15366 00598 ..598 BT BT 419 419 33 33 TTT |
This was expected to be a 463 sked. LW
The 20.00z 463 sked used 5020kHz rather than the expected 5018kHz (M01 is noted for this, Ed)
!!! Remember that M01 will change freqs & ID from 1 May :-
ID 025
| Sun | 07.00z | 6780kHz | ||
| Tue & Thur | 18.00z | 5280kHz | 20.00z | 4905kHz |
| Sat | 15.00z | 6434kHz |
Please use these in logs from 1st May 2004.
M03 General. Modes usually ICW, with a few in MCW, at about 17wpm except call “503” which is at a slow 5wpm. Each mssg is sent firstly with double 5fig gps then “call x 6” and mssg repeated with single 5fig gps.
Tx’s are mainly on weekday mornings between 07.00 - 13.00z at H, H+15, H+30, H+45 with the H & H+30 most usual.
GD on behalf of the E2K CW team produces a very detailed listing of the M03’s, available on request, which has already resulted in the discovery/confirmation of previously unknown or suspected skeds.
| M03 | Null format :- 044/00 (R5), [rarely R10]] ending = = 000 |
| Mssg format :- 044/54 (R5), [rarely R10] 54 x 5F, ending = = 000 | |
| M03a | With “triplet” element, only 111 or 333 so far logged, only Null Mssg logged. |
| Format :- 552/111 (333) /00, R5, [rarely R10] ending = = 000 | |
| Last logged May 2000, then arrives back April 2004. | |
| M03b | Mssg format only with gps in 50’s, with annual or year on year repeats. Repeats are sent on same Day/Time/ Freq and have been repeated for up to 5 years (so far).[ Why ? Ed] |
| M03c | Mssg format only with gps in 30’s and doublet “stutter groups” as the first and last 2 gps [eg 77777 77777] |
| No repeats ever logged. | |
| M03d | Mssg format only with > 60 gps, some having short period repeats. |
| ( has sent up to 133gps) | |
| M03e | Mssg format only with 71 gps (so far) and letter “R” between each gp and “RR” after each 10th gp. Recently discovered format |
.
Related voice members of the III family have similar formatting, eg E11’s, G11 (up to 1998) and S11a
Logs This station is really increasing its’ activity and coming up with a variety of surprises (Ed)
| M03c | Wed Mar 10th | 09.00z | 7377kHz | first and last two gps 77777, 77777. | Nice catch Gert |
| M03c | Mon Apl 26th | 09.00z | 7772kHz | ID 971/36, | Nice catch LW |
| 77777 77777 77777 77777 12334 12545 42548 44154 74454 42244 42222 25489 12548 63269 25780 01803 12035 22037 30959 03961 43078 46759 53210 64554 47666 02112 51558 55443 07771 50124 57203 05176 27740 45321 74847 84562 77777 77777 77777 77777 |
|||||
| Above repeated Thu Apl 29th, 10.00z, 8759kHz. LW | |||||
| M03c | Wed Apl 28th | 09.05z | 7378kHz | ID 211/32 | |
| BT BT 77777 77777 77777 77777 93875 29948 04881 45731 21847 92749 99449 84654 90458 95688 00495 59884 39000 48857 84990 11287 38372 13944 94587 09885 04958 03854 86745 20039 90388 49875 10055 38758 77777 77777 77777 77777 BT BT TTT |
|||||
| Above repeated Thu Apl 29th, 10.30z, 7984kHz, LW | |||||
M03, New entry/ confirmation, Wed Mar 31st, 09.15z, 8196kHz, clg 284/00 BT BT TTT, by LW
M03, the very elusive 121 sked, so it is still with us, heard by GD Sun Mar 28th, 19.10z, 6891kHz, clg 121/29 = 90769
| M03 | Wed Apl 7th | 07.22z | 6941kHz | with V’s till 07.30z then 508/00 BT BT TTT for 6 mins. | |
| 09.00z | 7377kHz | 214/00 | |||
| 09.15z | 8186kHz | 284/00 | |||
| 11.00z | 9610Hz | 186/00 | |||
| M03 | Fri Apl 16th | 07.30z | 6814kHz | 040/00 – add this slot confirmation into your lists. | Per LW |
| M03 | Mon Apl 19th | 09.30z | 5385kHz | 011/00 | Per GD |
| M03 | Fri Apl 30th | 11.00z | 7984kHz | 508/00 | Per LW |
| M03 | Tue Apl 20th | 08.30z | 8544kHz | 182/00 | |
| M03 | Tue Apl 27th | 07.40z | 10728kHz | 503/00 | |
| 08.30z | 8544kHz | 182/00 | |||
| 09.15z | 8196kHz | 284/00 |
Now here’s a real catch by LW, a M03a TRIPLET on a 121 sked, one of these has not been heard for a very very long time. It also challenges our previous thought that “121” was an “evenings only” TX, time to start looking very closely at this setup.
| Fri Apl 30th | 10.02z | 6891kHz | 121/111/00 BT BT TTT |
Other M3 freqs :- 4870, 5082, 6252, 4958, 6941, 7772, 8544, 10728
Wed Mar 10th, 07.00z 8136kHz in prog with good sig into Netherlands EU
Freqs reported, additional to Issue 21:-
3266, 7975, 8125, 10858, 10714, 12093 (New freq, CA) 12119
(MS reports that a number of the TX’s are under BC stations making copy difficult)
(CA reports that from 1 April the 12.00z & 13.00z skeds are back to:-
| 12.00z | |||||||||||||
| Mon | 9330 | Tue | 10858 | Wed | 9330 | Thu | 10858 | Fri | 9330 | Sat | none | Sun | poss 9330 |
| 13.00z | |||||||||||||
| Mon | 10566 | Tue | 12093 | Wed | 10566 | Thu | 12093 | Fri | 10566 | Sat | 12093 | Sun | poss 10566 |
This April change has been going on for past 6 years – MS
MS reports that the 18th Apl 11.00z TX’s on 9238 / 4173kHz sent OE & K instead of the usual AR & BT endings, also again on 21st 4173 / 10126kHz, this ending was last heard in early January 2004.
(subsequently more TX’s with this ending were heard on other skeds, Ed)
Tue Apl 20th, the expected 23.00z repeat of the 22.00z / 7526kHz TX did not arrive !!
The long standing Sat/Sun 16.30z 5078 // 7745kHz MCW 555 sked still with us.
| Mon Mar 8th | 21.03z | 4783kHz | CW, sent the 3 mssg 555 555 555 269 269 269 37 37 |
| 508 508 508 26 | |||
| 269 269 269 67 67 37 37 | |||
| Wed Mar 10th | 08.00z | 8190kHz | in prog |
| Wed Mar 10th | 12.00z | 8143kHz | clg 555 – 643 643 643 28 and 388 388 388 28 |
| Tue Mar 16th | 22.02z | 9164kHz | in prog, ended 32 32 41 41 TTT |
| Sun Mar 21st | 07.13z | 6512kHz | in prog, ended = = 217 217 34 34 TTT |
| Wed Mar 24th | 17.06z | 9164kHz | in prog, ended 17.18z = = 26 26 35 35 TTT |
| Sat Mar 27th | 07.03z | 9165kHz | CW, clg 555 555 555 475 475 475 25 then 475 475 475 15 15 25 25 |
| Thu Apl 1st | 19.55z | 9165//7745kHz | 555 832 28 555 |
| Wed Apl 14th | 12.00z | 8143//12227kHz | 555 297 19 122 29 555 |
| Thu Apl 15th | 08.00z | 5078//8190kHz | 555 859 41 432 38 555 |
| 19.00z | 6758kHz | “ | |
| Sat Apl 3rd | 07.01z | 9165kHz | TX but a keying fault made it unreadable |
| Thu Apl 8th | 18.07z | 5946kHz | in prog – inside the 49 Metre BC band. |
| Tue Apl 20th | 14.21z in prog | 8175kHz | ended 14.25z = = 98 98 33 33 TTT |
| Sat Apl 24th | 07.00z | 5946//9165kHz | 555 998 37 555 |
| Mon Apl 26th | 16.30z | 7745kHz | 555 571 30 275 21 049 19 435 25 555 a marathon session, per RN |
| Wed Apl 28th | 19.11z | 6758kHz | 03 03 26 26 635 635 635 04 04 22 22 |
Heard again, nice catch by Gert (his first for this one) TX in full.
Wed Mar 10th, 08.00z, 7891kHz.
Clg 111 111 111
95012 95012 95012 05 05 05
09197 09197 09197 05 05 05
pause
95012 95012 95012 25 25 05 05 = =
19048 05211 59477 09451 72328
= = 25 25 05 05
pause
09197 09197 09197 30 30 05 05 = =
37880 23082 00736 99591 46679
= = 30 30 05 05
With all the information included in this issue, particularly aimed at CW beginners, a comprehensive picture of M12 activity and scheduling may be obtained, and adapted for individual use.
| Thu Mar 11th | 05.40z | 7469kHz | in prog | |
| Thu Mar 11th | 19.43z | c7835kHz | in prog. | |
| Tue Mar 16th | 07.00/07.20z | 10713/12218kHz | ID 825 Null mssg. | |
| * | Sun Apl 25th | 03.00/03.20/03.40z | 8184 / 9184 / 10184kHz | ID 884 |
*MS reports that all 3 TX’s were good, and the first logging for a long while from his QTH
Recent logged skeds, per Gert & Anon :-
| March | |||||||||
| Mon | 06.30z | 9190kHz. | 07.10z | 14366kHz | |||||
| Tue | 07.00z | 10713kHz | ID 825 | 07.20z | 12218kH | ID 825 | 20.00z | 8171kHz | ID 152 |
| Fri | 19.00z | 10343kHz | ID 124 | 19.20z | 9164kHz | ID124 | 19.40z | 7849kHz | ID 124 |
| Sat | 18.30z | 12215kHz | ID 204 | 18.50z | 11054kHz | ID 204 | 19.10z | 9436kHz | ID 204 |
| Sun | 20.00z | 8157kHz | 20.20z | 7372kHz. | |||||
| April | |||||||||
| Tue | 18.20z | 10788kHz | 18.40z | 9088kHz | |||||
| Fri | 04.20z | 7488kHz | 04.40z | 9188kHz | |||||
| Sat | 18.30z | 14748kHz | ID 742 | 18.50z | 13437kHz | ID 742 | 19.10z | 12209kHz | ID 742 |
Additional to the above KoK logged :-
| Sat Mar 13th | 17.00z | 6782Khz | 749 000 |
| Mon Mar 22nd | 17.00z | 6782kHz | 748 1 1974 141 |
| 17.20z | 7657kHz |
PoSW remarks within his very extensive logs, here in edited form :-
| 20-Feb-04 | Friday | 2000 UTC | 6,782 kHz | |
| 2020 UTC | 5,876 kHz | S9+ signal over-riding BC station inside the 49 metre band - "263 263 263 000” | ||
| 21-Feb-04 | Saturday | 1500 UTC | 15,862 kHz | this schedule noted last Saturday - "853 853 853 1", DK/GC "772 113" x 2. Repeated 1520z, 14,522 kHz and 1540z, 13,384 kHz. All three sendings very strong signals. |
| 1830 UTC | 10,826 kHz | "841 841 841 1", DK/GC "152 157" x 2, signal strength S7. Repeated 1850z, 9,449 kHz, difficult copy due to location inside 31 metre BC band and 1910z, 8,128 kHz, S9+, strongest sending. | ||
| 22-Feb-04 | Sunday | unable to find any sign of the early morning M12 schedule starting at 0740z, 13,484 kHz, call "134"; noted on previous Sundays in this month. | ||
| 23-Feb-04 | 1834 UTC | 10,826 kHz | transmission in progress, strong signal, same frequency as noted active on Saturdays; at 1836z started sending "841 841 841 2" - two message M12 - then second DK/GC "566 83" x 2, ended "000 000" 1843z. | |
| 1850 UTC | 9,449 kHz | second sending . 1910 UTC, 8,128 kHz, third sending | ||
| 24-Feb-04 | Tuesday | 1800 UTC | 8,084 kHz | long standing Tuesday and Friday schedule, "462 462 462 1", DK/GC "219 113" x 2, S9 signal with key clicks. |
| 1820 UTC | 6,856 kHz | repeats | ||
| 1840 UTC | 5,788 kHz | |||
| 2000 UTC | 6,782 kHz | "263 263 263 000" - same schedule as noted on Fridays during this month - both sendings very strong, S9+ signals. | ||
| 2020 UTC | 5,876 kHz | |||
| 25-Feb-04 | Wednesday;- | 2000 UTC | 7,717 kHz | "413 413 413 1", DK/GC "820 261" x 2, fast CW as observed on 9,046 kHz, at 19.55z. No doubt so as to fit this much longer than average message into a 20 minute slot. |
| 27-Feb-04 | Friday | 1806 UTC | 8,084 kHz | first sending of the "462" schedule in progress, S9 signal with key clicks. |
| 1820 UTC | 6,856 kHz | repeats of "462", DK/GC "219 113" x 2, same as when this schedule last appeared on Tuesday ; unusual for this "462" to send the same message two transmissions in a row. | ||
| 1840 UTC | 5,788 kHz | |||
| 28-Feb-04 | Saturday | 1500 UTC | 15,862 kHz | "853 853 853 000", strong signal. |
| 1830 UTC | 10,826 kHz | "841 841 841 1", DK/GC "306 117" x 2, strong signal. | ||
| 1850 UTC | 9,449 kHz | strong enough to over-ride BC station, and 1910 UTC, 8,128 kHz, S9+, repeats of "841" and "306 117". | ||
| 4-Mar-04 | Thursday | 0650 UTC | 13,366 kHz | "133 133 133 1", DK/GC "453 50" x 2; the early morning Thursday and Monday schedule continues on new frequencies in March. |
| 5-Mar-04 | Friday | 1800 UTC | 8,084 kHz | the Friday and Tuesday "462" schedule continues in March, DK/GC "7298 141" x 2. Repeated 1820z, 6,856 kHz and 1840z 5,788 kHz with the usual key clicks. |
| 6-Mar-04 | Saturday | 1830 UTC | 12,215 kHz | "204 204 204 1", DK/GC "365 63" x 2, weak signal. |
| 1850 UTC | 11,054 kHz | strength S7, and 1910z, 9,436 kHz, strong signal inside 31 metre band, repeats of "204" and "365 63". This "204" schedule ran in March last year. | ||
| 8-Mar-04 | Monday | 0630 UTC | 12,166 kHz | "133 133 133 2" - a two message transmission, usual format, first DK/GC "349 40" x 2, second DK/GC "453 50" x 2. |
| 0650 UTC | 13,366 kHz | "133 133 133 2" again. | ||
| 11-Mar-04 | Thursday | 0650 UTC | 13,366 kHz | "133 133 133 2" and "349 40" x 2 - same as on Monday. |
| 13-Mar-04 | Saturday | 1830 UTC | 12,215 kHz | "204 204 204 1", DK/GC "3062 89" x 2. Repeated 1850z, 11,054 kHz and 1910z, 9,436 kHz,. |
| 16-Mar-04 | Tuesday | 2040 UTC | 5,752 kHz | "152 152 152 1", DK/GC "365 79" x 2, strong signal. |
| 18-Mar-04 | Thursday | 0650 UTC | 13,366 kHz | "133 133 133 1", DK/GC "191 121" x 2. |
| 20-Mar-04 | Saturday | 1830 UTC | 12,215 kHz | "204 204 204 2", a two-message transmission, weak signal, difficult copy, first DK/GC "312 ???" x 2, second DK/GC "420 71" (?) x 2. Transmission ended after 1850z. |
| 1855 UTC | 11,054 kHz | 1855 - and 40 seconds UTC, running late due to length of time taken by two messages - 11,054 kHz second sending of "204", much better signal than the first sending, DK/GC "312 191" x 2, second DK/GC "420 71" x 2. | ||
| 1921:20s | 9,436 kHz | "204" third sending with BC QRM. | ||
| 21-Mar-04 | Sunday | 2000 UTC | 8,157 kHz | "557 557 557 1", DK/GC "7196 259" x 2, long message, strong signal with deep QSB. Unable to find any further sendings, may have been the third transmission. |
| 22-Mar-04 | Monday | 0651 UTC | 12,166 kHz | the first sending of the "133" schedule; surprised to find it still in progress at 0651z, 21 minutes after the start time - the second sending on 13,366 kHz would normally be up at 0650z. Must be a very long mesage this morning! |
| 0700 UTC | 13,366 kHz | "133 133 133 2" - two mesages this morning which is why everything is running late, first DK/GC "6145 183" x 2. | ||
| 23-Mar-04 | Tuesday | 2020 UTC | 6,865 kHz | both S9+ signals, "152 152 152 1", DK/GC "365 79" x 2, same as last Tuesday. |
| 2040 UTC | 5,752 kHz | |||
| 25-Mar-04 | Thursday | 0650 UTC | 13,366 kHz | "133 133 133 1", DK/GC "900 149", strong signal. |
| 26-Mar-04 | Friday | 1900 UTC | 10,343 kHz | "124 124 124 1", DK/GC "1640 143" x 2, strong signal with key clicks. |
| 1920 UTC | 9,164 kHz | repeats | ||
| 1940 UTC | 7,849 kHz | |||
| 27-Mar-04 | Saturday | 1721 UTC | 14,515 kHz | just caught the end of the call-up, "754 754 754 1", DK/GC "582 143" x 2, strong signal. A chance discovery, this; I had just been checking out the 20 metre amateur band to see what might be heard on the last evening before the start of summertime. On finding nothing but mainly S9+ Eastern European stations calling "CQ Contest" right across the band I happened to tune a bit H.F. and found M12! |
| 1740 UTC | 13,421 kHz | "754" and "582 143" again, very strong signal. Must be the second and third sendings of a transmission which has been running during March. | ||
| 1830 UTC | 12,215 kHz | first sending of the "204" schedule, very weak signal, unable to make out the DK/GC | ||
| 1850 UTC | 11,054 kHz | "204 204 204 1", DK/GC "5847 137" x 2, much stronger signal than the first sending. 1910 UTC, 9,436 kHz, third | ||
| 3-Apr-04 | Saturday | 1831 UTC | 14,748 kHz | just caught the end of the call-up, "742 742 742 1", DK/GC "427 203" x 2. The CW seemed to be faster than usual for an M12, no doubt to fit this longer than usual message into the twenty minute slot and allow a few minutes over. |
| 1850 UTC | 13,437 kHz | "742" and "427 203" again, strong signal but the Morse had a "Hollow" and difficult to read effect, perhaps due to multi-path propagation. | ||
| 1914 UTC | 12,209 kHz | must be the third sending of the "742" schedule in progress, again with a propagation effect making for difficult reading. | ||
| 4-Apr-04 | Sunday | 0704 UTC | 10,639 kHz | 8.04 AM BST, M12 CW in progress, ended "000 000" just before 0706z |
| 0720 UTC | 12,139 kHz | "261 261 261 1", DK/GC "6729 58" x 2, signal strength only S5 at best. I was unable to find a Sunday early morning M12 in March despite a lot of tuning around; surprised to find a transmission this low in frequency, Sunday M12s around this time have always been found in the 14MHz or higher bands. | ||
| 5-Apr-04 | Monday | 0530 UTC | 9,108 kHz | "122 122 122 1", DK/GC "1463 177", strong signal with some QSB. |
| 0550 UTC | 11,208 kHz | "122" and "1463 177" again; looks like the same frequency schedule which ran on Mondays and Thursdays in April 2003. | ||
| 1830 UTC | 14,748 kHz | "742 742 742 1", DK/GC "800 135" x 2. Same schedule as noted on Saturday, see above; and looking back through the log book also noted in April 2003. | ||
| 1850 UTC | 13,457 kHz | repeats of "742" and "800 135" | ||
| 1910 UTC | 12,209 kHz | |||
| 6-Apr-04 | Tuesday | 1840 UTC | 9,088 kHz | "488 488 488 1", DK/GC "517 141" x 2 |
| 8-Apr-04 | Thursday | 0530 UTC | 9,108 kHz | "122 122 122 1", DK/GC "1463 177" x 2, same as on Monday. Repeated 0550z, 11,208 kHz and 0610z, 12,208 kHz. |
| 9-Apr-04 | Friday | 0602 UTC | 9,129 kHz | last few seconds of "146 146 146 000", ended 15 seconds after 0602z, very strong signal. |
| 0620 UTC | 10,429 kHz | a search for a second sending of "146 146 146 000" found this very strong signal. | ||
| 11-Apr-04 | Sunday | 0640 UTC | 9,239 kHz | "261 261 261 1", DK/GC "382 111" x 2, strong signal. |
| 0700 UTC | 10,639 kHz | repeat sending | ||
| 0720 UTC | 12,139 kHz | |||
| 1940 UTC | 12,212 kHz | "128 128 128 1", DK/GC "1471 185" x 2. | ||
| 2000 UTC | 11,125 kHz | repeat | ||
| 12-Apr-04 | Monday | 0530 UTC | 9,108 kHz | "122 122 122 1", DK/GC "423 139" x 2, signal strength S7 at best, QRM from a wide-band buzz centered on 9,116 kHz. |
| 0550 UTC | 11,208 kHz | second sending of "122" schedule with a TX problem; on tuning in this frequency shortly before 0550z for the expected second sending there was a massive S9+ carrier up and at 0550z the clicks of keyed Morse could be heard but the carrier remained un-interrupted . This continued until approx. 0552z when the carrier vanished and the "122" call started up and the transmission proceeded as normal. | ||
| 0610 UTC | 12,208 kHz | third sending | ||
| And something a bit different on this Easter Monday morning;- | ||||
| 0539 UTC | M12 but NOT the usual CW mode, was constant carrier keyed tone MCW, and this too had problems. Calling "903 903 903 1", then DK/GC "138 66" x 2 just before 0540z. The Morse suddenly stopped at 0543z although the carrier remained on - I kept watch on another receiver while following the progress of the "122" M12 schedule. Started up again with "903 903 903 1" again around 0550z and went into 5Fs without the DK/GC. Ended "000 000" 0556z and carrier went off a few seconds afterwards. I have heard M12 in MCW before but not recently; no doubt this mode has the advantage that it can be copied with a receiver not equipped with a BFO, a domestic radio with a short wave band as opposed to a communications receiver. | |||
| 18-Apr-04 | Sunday | no sign of the early Sunday morning M12 schedule; made a point of listening for the second sending expected at 0700 UTC, 8 AM BST on 10,639 kHz, noted on previous two Sundays in April, but heard nothing. Not the first time an M12 schedule has vanished half way through the month. | ||
| 1935 UTC | 13,457 kHz | "840 840 840 1", DK/GC "3681 203" x 2, long message, very strong signal. | ||
| 1955 UTC | 12,086 kHz | "840" and "3681 203" again, S9+ signal inside 25 metre band, no BC QRM, must be the second and third sendings of a schedule; no doubt the first sending is 1915z, 14,8 something kHz. | ||
| 19-Apr-04 | Monday | 1942 UTC | 12,151 kHz | just caught the DK/GC at the end of the call-up, "3186 179" (?) x 2, strong signal. |
| 20-Apr-04 | Tuesday | 0540 UTC | 9,126 kHz | early morning M12s seem to be more widespread these days - "891 891 891 1", DK/GC "813 45" x 2. |
| 0601 UTC | 9,129 kHz | and another one! - the receiver had been left on 9,126 after the above and just after the hour the distinct rhythm of M12 activity could be heard again; when tuned in was on a frequency just 3 kHz higher than the earlier transmission, "146 146 146 000", very strong signal. | ||
| Sat Mar 6th | 05.00z | 6642kHz | 284 (R5) BT 234 22 BT |
| Sun Mar 7th | 05.30z | 5288kHz | 411 (R5) BT 259 20 BT rpt of 6th , 05.30z 5288kHz “ 411 (R5) BT 259 20 BT 52804 4838. …15 37807 60695 49403 24537 31823 43932 15396 15218 19295 29012 03134 59447 53429 23769 45166 03.12 17427 BT 000” |
| Sun Apl 4th | 04.30z | 5474kHz | 411 (R5) BT 260 21 BT |
| Thu Apl 8th | 21.00z | 7947kHz | 254 (R5) BT 245 21 BT |
| Fri Apl 9th | 20.03z | 12218kHz | 714 sked was expected to have been BT 234 nn BT, it sent BT 235 22 BT, nicely caught by LW |
| Mon Apl 12th | 19.00z | 7735kHz | 417 (R5) BT 235 12 BT |
| Thu Apl 22nd | 20.00z | 12218kHz | 714 (R5) BT 235 22 BT |
| Wed Apl 28th | 21.00z | 4774kHz | 346 (R5) BT 233 22 BT |
Freqs reported, additional to Issue 21:-
4715, 6327, 6884, 7432, 8183, 8186, 9348, 9877, 10214, 10284, 10887, 10926, 12218, 12397, 12445
| Tue Mar 9th | 21.00z | 7993kHz | MCW. “ ‘158’ 000 –241 21 “ |
This 2nd/4th Sat/Sun of month variant caught by LW
| Sat 13th Mar | 22.07z | 3575kHz | in prog ending 22.15z, very slow, clg 510 |
| “282 21 BT 34858 64822 16843 01699 05628 39978 51734 11248 03164 64922 34749 25657 64875 31025 52137 35088 51763 55712 58410 61849 22404 BT TTT” |
|||
| Sun 29th Mar | 21.02z | repeat of above, postamble rptd x 4 | |
| Sun 11th Apl | 21.02z | 4031kHz | 831 rptd BT 283 20 BT |
| Sat/Sun 24th/25th Apl | above repeated. LW & RN | ||
The expected TX’s for 16th/17th & 24th/25th Apl were NRH
MCW First & third Fri Sked
| Fri Mar 5th | 20.00z | 6785kHz | clg 263 DK/GC 158 158 29 29 = =, with the now expected less than perfect spacing of this sked and S9+ sig. Resend at 21.00z on 5810kHz. |
| Fri Mar 19th | 20.00z | 6758kHz | null mssg “263 263 263 00000” |
| Fri Apl 2nd | 20.00z | 9060kHz | clg “263 DK/GC 819 819 54 54 = =” |
Back again after a long rest, being widely heard in EU (March) with good signal
| Mar 9th | 18.50z | 4073kHz |
| Mar 13th | 22.15z | 4073kHz |
KoK catches these
| Tue Mar 9th | 20.34z | c7795kHz | 666 = 37 37 = |
| Tue Mar 23rd | 20.04z | 7800kHz | 246 = 25 25 = |
| Wed Mar 24th | 17.00z | 6782kHz | 749 1 8579 136 with repeat at 17.20z on 7656kHz – broken by an FSK on same freq sending 5f code which changes to RTTY, stops to send XXX in CW then continues with RTTY. |
Followed by a nice catch from LW (his first), a 25gp message (poss repeat of KoK 23rd)
Wed Mar 24th, 20.07z in prog, 7994kHz, ended 20.12z
….. ….. 30830 98686 22673 BT IMI IMI BT
94413 02216 03803 91851 23234 97988 96280 81251 27636 35403
84185 80030 60486 12225 96597 23364 13216 18938 91056 74095
48677 40074 30830 98686 22673 BT AR AR
Another station that appears to be increasing its’ output, two mssgs in a month rather than the null mssgs of late, and a later timeslot.
Really going into overdrive, heard by GD on
| Mon Mar 1st | 11.30z | 12070kHz | |
| 12.00z | 10471kHz | ||
| Tue Mar 2nd | 18.00z | 9125kHz | |
| 18.30z | 10555kHz | ||
| Wed Mar 3rd | 19.30z | 9060kHz | other sending prob 19.00z |
| Thu Mar 4th | 08.00z | 10205kHz | other sending prob 07.30z |
By LW & GD
| Mon Mar 22nd | 11.30z | 12070kHz | |
| 12.00z | 10469kHz | severe QSB at LW, clear with GD | |
| Mon Mar 29th | 11.30z | 12070kHz | |
| 12.00z | 10469kHz. | ||
| Tue Mar 30th | 18.00z | 9125kHz | virtually unreadable (LW) |
By PoSW
| Tue Mar 2nd | 18.37z | 10555kHz | in prog, sent Very fast ending “ = = 751 751 90 90 00000”, probably to get all gps into the time slot. |
M24 now 1 hour earlier, Mon 10.30 / 11.00z , Tue 17.00 / 17.30z same freqs.
This elusive little devil is still with us, a nice catch by GD
| Thu 22 Apl | 19.24z | 4030kHz | 968 x 3 28623 x 3 sent twice |
| 968 x 3 27430 x 3 sent twice |
| Tue Mar 9th | 01.12z | 9075.5kHz | in prog, clg NR 03 M 0902: 13: 35 2004 BT. |
By JPL Ontario, a nice catch from “over the pond”
And by Kok
| Mon Mar 22nd | 19.32z | 4635 // 5115kHz | in prog. |
| Thu Mar 25th | 23.14z | 5115kHz | in prog |
This one’s starting to pop up with some regularity !! heard by LW
| Fri Apl 2nd | 13.05z | 12150kHz |
| Mon 12th Apl | 22.30z | 4699kHz | Clg “vvv jvg jvg jvg de bml bml bml qsa3 qsa? Qtc 521 (R2) |
cut , hand (mainly heard by IB)
| Thu Mar 18th | 01.30z | 9846kHz | CW , null mssg , 249 249 249 000 000 (r10) ttt |
| Fri Mar 19th | 06.30z | 11250kHz | MCW, in prog, “ 945 945 945 333” “03 03 50 50” & “ 04 04 50 50” |
| Wed Mar 31st | 23.00z | 10518kHz | MCW with :- |
| 651 x 10, 651 x 10, 651 x 7, 651 x5 all ending 000 | |||
| Thu Apl 1st | 07.00z | 13000kHz | CW with :- |
| 792 x 15, 792 x 8, 792 x 6 all ending 000 | |||
| Fri Apl 30th | 06.30z | 11248kHz | in prog. |
| ….. 954 x3 333 x2, 945 x14 333 x2, 945 x8 333 x2, 945 x 12 333 x2, |
| Sat Mar 13th | 21.55z | 4073kHz | Marker D3EU |
Auto, long zero, no cuts, 15wpm.
AB alerted E2K to this station, initially being heard in the US, but also received in Europe.
| 21.00z | 14376/7kHz | Tue/Thu/Fri |
Interesting station as reception is reported as being very poor and noisy with severe fade and flutter both in US & Europe for the same TX .
Signal so poor that with up to 5 experienced monitors listening to each TX it was not possible to 100% decipher all the groups. Here is what we managed, possible alternative in ( ) :-
35254 44487 80904 10966 33450 79574 98086 33550 73592 08294
49036 12587 19002 77918 76010 61003 02875 16100 63145 57. 8 .
06138 43981 15847 38332 57292 68579 88330 96040 15875 51610
34691 01193 68204 73565 34275 79196 67656 23092 59354 81144
15454 57326 00425 65991 93218 53985 (43985) 67418 87994 43939 13360
51515 60645 77419 39565 24983 31499 87962 72726 90182 53018
33182 07769 72930 10008 65424 14440 59670 73511 91082 72635 (72615)
44433 22126 51207 91258 (91256) 11807 68514 30582 74570 45107 (45197) 87763
57715 04051 42414 021.7 53647 96146 (96046) 81781 35698 25498 02154
98745 36587 36954 25847 48756 25874 (25847) .9847 23658 58475 03695
34587 02541 69587 34797 (34897) 98745 65479 21452 11115 36985 (36981) 48598
59847 62313 75412 85479 92587 05874 36589 01114 19874 24789
36984 45621 56984 62314 78954 82136 94568 12354 26513 32541
45699 55694 65894 78955 82265 93254 05642
/ / AR
Note that 98745 is a repeated group, not a receive error as ALL monitors logged it.
Sincere thanks to GD, LW, MoK, MS & CWanon for this great effort.
First logged April 8th and heard on 13th, 15th, 16th & 22nd sending the same 137 gp mssg, it was possibly a daily TX but no reports received for Mondays, Wednesdays or weekends despite intensive monitoring.
Not heard since 22nd April so may be a “special event” station, that has now done its’ job.
The TX of 16th had a very odd “ring” to it and when MoK displayed the sig on an RF Signal Analyzer there were distinct “shadow sigs” at –400Hz and +1000Hz all in perfect sync, the AF analyzer later confirmed this from a short recording.
On the TX of 22nd a weak “long path” delayed sig was clearly heard in the background by MoK .
Format:-
V’s for 45 secs (hrd once for 2 mins), call M6 x 4, single 5 fig gps, ends / / + (/ / AR) then off immediately.
Interestingly since 22nd Apl an XJT type signal has been using this freq regularly with some TX’s going on for hours and, at times, displaying the same fade/flutter.
Worth keeping an eye on.
AB, CA, GD, Gert, IB, JPL, KoK, LC, LW, MS, ML, MoK, PoSW, PP, RN, Cwanon, Anon2 UK.
Morse stations | Voice stations | Oddities | Polytones
Numbers predictions | Non numbers | Propagation Indicator
How random is random ? | The Czechoslovakian government in exile - WWII
News Items | Web sites | Requests | Stop press | Contribution deadlines
Index | E2K NL Home
![]()