M0JQQ — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving M0JQQ, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-08-23 and 2026-08-24.
These are automated observations at the SO8OO receiver, not an official contact log. Times are UTC. Attribution follows decoded FT8 message structure: CQ uses the first token and directed-looking messages use the second. Free text that resembles a directed message can be attributed imperfectly. Summary S/N reflects propagation plus SO8OO receiver, antenna and local-noise conditions. Counts are not adjusted for monitoring outages; transmissions that were not decoded are absent. Inferred entity and location data may be inaccurate for portable, remote or special-event operation.
SO8OO decoded 3 FT8 messages attributed to M0JQQ as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The available sample contains attributed decodes on 20 m (100%). The sample is too small to infer a recurring UTC-hour or received-S/N pattern.
Overview
Observed FT8 message patterns
- Attributed sample
- 3 messages
- Active dates
- 2 UTC dates
- S/N summary
- Too few decodes
- S/N percentile sample
- Too small
- Recurring-pattern threshold
- Not met
WSJT-X defines S/N reports against a 2,500 Hz reference noise bandwidth. The ranges above are SO8OO receiver-side display categories, not official WSJT-X classes, transmitter-power measurements or estimates of how easy the station is to hear elsewhere. Statistics include only successful decodes on SO8OO's monitored FT8 channels; transmissions that were not decoded are absent. The sample does not meet the threshold for a recurring time or signal-pattern claim (20 attributed messages, three UTC dates and five distinct 15-minute windows).
Frequent counterpart tokens observed at SO8OO
Tokens most often paired with M0JQQ in decoded directed-looking exchanges:
Most frequent locator attributed to M0JQQ
The map compares the centres and boundaries of the locator field attributed to this token by decoded message structure, 2° × 1° as a Maidenhead square, and SO8OO's six-character receiver square. The separation is not an exact antenna-to-antenna distance or a radio-path length.
- Attributed locator
- IO95
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,646 km (approx.)
- Last such locator decoded
- 2026-08-24 09:33 UTC
A decoded locator can describe portable, remote or special-event operation and is not proof of a permanent station address or transmitter identity.
Observed FT8 exchanges
S/N cells show: decoded at SO8OO / report transmitted by the counterpart. An observed exchange is not a QSL or an official logbook confirmation.
| Time UTC | Band | M0JQQ S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-24 09:39 | 20m | - / - | F4BYA | +2 / - | 3 | Partial capture |
| 08-23 09:56 | 20m | -16 / - | EA5ISM | - / -12 | 2 | Partial capture |
| 08-18 10:39 | 20m | - / -20 | ON4DS | 0 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 103930 -2 796 M0JQQ ON4DS -20 (x2) 095645 -15 2008 EA5ISM M0JQQ R-12 (x2) 093330 -19 2194 PD4RJ M0JQQ IO95 093445 +3 2430 M0JQQ F5HNQ IN98 093945 +0 2915 M0JQQ F4BYA JN19 (x3)
Decoder S/N history by band
Count-weighted daily averages across messages attributed to this profiled token and successfully decoded at SO8OO, limited to the rolling 90-day UTC chart window.
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee