J,
I have a working theory that there were two (or more) networks active at the same time.
You reported mostly the same frequencies as I did. Except you reported 11225 and 11300 kHz being heard that were not on my original list. In my post I added an edit that several other freqs had been found and it included both of those freqs, as well as 4 others.
Those “added” freqs I could only hear on remotes, not locally. But several, maybe all, of them appeared to be greatly out of time with the signals I was hearing locally. They all had the same approximate 124 msec pulse being sent every 6 seconds, but the pulses appeared significantly delayed. Because of the unpredictable lag in remotes this does not mean much by itself, however one of the remotes (located in CO) could receive both 13325 kHz (that I could hear locally) and 13350 kHz (I could not hear locally) dits on the same waterfall, and there appeared to be several seconds between them on the waterfall.
The same CO remote was able to display three pulses at the same time, 13250, 13325, and 13350 kHz. 13250 and 13325 kHz showed the same spacing as I was seeing locally, 13325 kHz pulsed immediately after 13250 kHz. However 13350 kHz appeared to pulse roughly 3 or 4 seconds after the other two, or if you prefer 2 or 3 seconds before the other two frequencies. Also, while 13250 and 13325 kHz were approximately the same signal strength on the remote the 13350 kHz signal was significantly weaker.
I got the impression that 13350 kHz was from a different source than 13250 and 13325 kHz.
In the past once or twice double dits have been noted. Say the spacing of events is 6 seconds but instead of one pulse per cycle two pulses were noted, separated by a second or two. I am thinking that maybe there are multiple sources, and the pulse from each source is staggered so that they do not end up on top of each other.
If the 16 frequencies I saw were all in one network and that was all of the frequencies in that network then a complete cycle, transmitting an individual pulse on each freq in sequence, should have taken just under 2 seconds. My timing images (posted in the other thread) show I missed at least one freq. This would put the cycle at a tad over 2 seconds. Lets say I missed a couple of others also. At 0.124 sec per freq there could have been 24 freqs and still complete the cycle in under 3 seconds.
So, my theory is that possibly, just maybe, there were two networks working in sync. One network used the first half of the 6 second window (0.0 to 2.999 sec) and the other network used the second half of the 6 second window (3.0 to 5.999 sec).
T!