HFU HF Underground

Loggings => Spy Numbers => Topic started by: Token on January 01, 2019, 0317 UTC

Title: V24 logs, January 2019
Post by: Token on January 01, 2019, 0317 UTC
All, the last couple of months we have had multiple V24 logging threads, and they got a bit scattered with multiple freqs / days / times in each thread.  It might be a bit better if everyone posted their January, 2019, V24 logs in one thread.   Possibly this one thread ;)

If this works out it should result in all V24 Jan 2019 logs in one easy to find place.

Here is my latest V24 schedule.  Keep in mind several of these freqs have been skipped in the last couple of months, but every time I take them off the sched they come back for a month or two.

(http://www.tokenradio.net/Radio/SharedFiles/NumbersTfer/V24_sched_V_21_0_4Q_2018.JPG)

T!
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 01, 2019, 1550 UTC
01/01/2019, 1530 UTC, 6310 kHz, weak signal but usable in Denver. Music 1530-1533, OM speaking 1533-1540, QRT 1540.
Title: Re: V24 logs, January 2019
Post by: Token on January 01, 2019, 1641 UTC
I still say it is a slightly deep female voice and not an OM ;)

My video of this mornings V24 transmission (01 January, 2019, 1530 UTC, 6310 kHz).
https://www.youtube.com/watch?v=C7WNy3pWjhc

T!
Title: Re: V24 logs, January 2019
Post by: Josh on January 02, 2019, 2036 UTC
FORMAT SPECIFIER: Call to an individual station
ADDRESS (Ship): 367 835000
COUNTRY: United States of America
CATEGORY: Safety
SELF IDENTIFICATION (Ship): 372 545000
TELECOMMAND 1: Test
TELECOMMAND 2: No information
CALLED STATION RECEIVE FREQUENCY: No information
CALLED STATION TRANSMIT FREQUENCY: No information
ACKNOWLEDGEMENT: Call requires acknowledgement
Checksum OK
FORMAT SPECIFIER: Call to an individual station
ADDRESS (Ship): 367 835004
COUNTRY: United States of America
CATEGORY: Routine
SELF IDENTIFICATION (Ship): 372 544000
TELECOMMAND 1: Test
TELECOMMAND 2: No information
CALLED STATION RECEIVE FREQUENCY: No information
CALLED STATION TRANSMIT FREQUENCY: No information
ACKNOWLEDGEMENT: Call requires acknowledgement
Checksum not OK


Sorry couldn't help myself.
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 03, 2019, 1607 UTC
03 JAN, no copy at all of anything at 5290 5Hz 1430 UTC, but only tried with my own rx. Maybe it was on, maybe it wasn't - someone else will have to say.

6310 @1530z was about the same as it was on New Year's Day, perhaps even slightly more tenuous but still audible.

@T!, maybe an 85 year old woman recorded the numbers, but I find that implausible. :D
Title: Re: V24 logs, January 2019
Post by: shadypyro on January 04, 2019, 2012 UTC
Hopefully i will be able to wake up before 14:30 UTC (6:30 AM my time) tomorrow to catch 5290 kHZ
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 04, 2019, 2310 UTC
Hopefully i will be able to wake up before 14:30 UTC (6:30 AM my time) tomorrow to catch 5290 kHZ

I haven't seen any reports that it was on the other day. If it wasn't transmitted on the 3rd, it won't be on the 5th or 7th either. But hopefully 6215 will be on at 1500. Being further east, that broadcast has proven the best copy, likely because it's the second highest frequency they use and they use it 30 minutes earlier than 6310. In past winters they have not used it in January, though. We'll see what happens.
Title: Re: V24 logs, January 2019
Post by: Token on January 05, 2019, 0022 UTC
Hopefully i will be able to wake up before 14:30 UTC (6:30 AM my time) tomorrow to catch 5290 kHZ

The last time they used 5290 kHz was in October of 2018, and they did not use it on the 3rd  of this month.  So, as MDK2 said, it probably will not be used on the 5th or 7th.

However, 6215 kHz at 1500z was used last month, and is very likely to be used this month.  So look for it at 1500z, on 6215 kHz, on the 5th, 7th, and 9th.

T!
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 05, 2019, 1501 UTC
05 January, nothing either for 5290 @ 1430 or 6215 @ 1500.
Title: Re: V24 logs, January 2019
Post by: Token on January 05, 2019, 1523 UTC
05 January, nothing either for 5290 @ 1430 or 6215 @ 1500.

And looking at the past logs, 6215 kHz at 1500z has not happened in January for the last 3 years.  However 5290 kHz at 1430z did happen during that time periods.

If both of those time slots are out this year, the next historic V24 transmission will be 6310 kHz at 1530z on the 8th.

4925 kHz may, or may not, (it was reactivated in Dec after a period of inactivity) be used at 1430z on 11, 13, and 15.

The 1600z slots on 5115 and 5900 kHz are pretty safe and dependable, starting from the 11th.

5715 kHz at 1500z appears to have reactivated in Dec, so it may be up this month on the 19, 21, and 26.  But this slot has always been very hit or miss, often skipping months.  For example, last year it was active on months 1, 2, 3, 7, 8, 10 and 12, but not on months 4, 5, 6, 9, or 11.

5150 kHz at 1400z on 18, 21, and 25, really appears terminated.

And 4900 kHz at 1530z on 23, 25, and 27, co-channel with the BC station, appears relatively dependable, but can be hard to hear under the BC at some locations.

I would say there is a good chance of 9 more V24 transmissions this month, possibly, but unlikely, as many as 15.

I have really thought, for some time, that V24 might have some unknown / unreported times and freqs in use.  Some months there can be VERY little activity on the known freqs / times.

T!
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 08, 2019, 1628 UTC
01082019, 6310 AM, 1530 UTC, V24 was almost a fair signal here, making it the best copy of the month for me so far.
Title: Re: V24 logs, January 2019
Post by: Ary-B on January 15, 2019, 1501 UTC
4925   15-01-2019 1430 V24    AM   piano music followed by a message in Korean

Ary
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 18, 2019, 1413 UTC
18 JAN, 1400 UTC, 5150 had a carrier up by 1350z, music and message at 1400z, carrier off at 1409z. Weak signal despite solid carrier in Denver, but sounded pretty good in spite of radar (possibly OTHR) QRM on the Chiba "soy sauce" kiwi SDR in Japan.
Title: Re: V24 logs, January 2019
Post by: Nomadiq on January 18, 2019, 1421 UTC
18 JAN 1400 UTC 5150 Carrier also seen on Northern MD and Mojave Desert SDRs. Mojave SDR hit by OTHR. Nagano, JP SDR had V24 very strong but also impacted by OTHR.
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 18, 2019, 1622 UTC
18 JAN, 1600 UTC, 5900 AM, V24 was poor to fair but usable into Denver. K-pop song at 1600z, Korean numbers at 1603z, message over and carrier QRT at 1610z.
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 19, 2019, 1512 UTC
19 JAN, 1500 UTC, 5715 AM, V24 weak in Colorado, also weak on the Chiba "soy sauce" SDR (wide skip zone perhaps?), but clear and copyable on Token's Mojave SDR on the kiwi network. I almost forgot about this and didn't tune in until about 1503, so I missed the music. Korean numbers read until 1512z, QRT at that time.
Title: Re: V24 logs, January 2019
Post by: Token on January 19, 2019, 1640 UTC
I really like that V24 has kept 5715 kHz operational.  That may be the oldest used numbers station frequency active today, and as far as I know has been pretty much continuously active.  Records of Korean numbers, often presumed to be South Korean, go back to the mid 1970's.  I know the first time I heard V24 it was on this frequency.

T!
Title: Re: V24 logs, January 2019
Post by: Ary-B on January 21, 2019, 1504 UTC
5150   21-01-2019 1403 V24  Message in Korean
5715   21-01-2019 1500 V24  Music followed by a message in Korean

Ary
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 22, 2019, 1616 UTC
22 JAN, 1600-1609 UTC, 5900 received with poor to fair quality at KPH kiwi SDR in California, and JBA at my own QTH.
Title: Re: V24 logs, January 2019
Post by: Ary-B on January 25, 2019, 1409 UTC
5150 kHz 1400 UTC V24 AM Music followed by a message in Korean

Ary
Title: Re: V24 logs, January 2019
Post by: MDK2 on January 26, 2019, 1510 UTC
26 JAN, 1500 UTC, 5715 AM, weak signal in Denver. Good but noisy on Chiba "soy sauce" SDR in Japan. Good and mostly clean, but some adjacent radar QRN on Token's kiwi SDR in the Mojave Desert. Presumed repeat of message sent on previous broadcasts used on this time/frequency slot.