9K2NO — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving 9K2NO, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 80m, across 2 UTC dates in the available aggregate history. Observed between 2026-08-31 and 2026-09-01.
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 9K2NO as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The available sample contains attributed decodes on 80 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).
Most frequent locator attributed to 9K2NO
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
- LL38 · 2 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 3,194 km (approx.)
- Last such locator decoded
- 2026-09-01 16:48 UTC
Other locator fields attributed to this token: LL39 (1).
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 | 9K2NO S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-01 17:06 | 80m | - / - | R2SN | +1 / - | 4 | Partial capture |
| 09-01 16:49 | 80m | - / - | OH3NXW | -1 / - | 5 | Partial capture |
| 09-01 16:48 | 80m | -24 / - | RI1FJL | - / - | 2 | Partial capture |
| 08-31 20:32 | 80m | - / - | M7GFJ | -16 / - | 12 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 203800 -14 721 9K2NO M7GFJ IO80 (x3) 164815 -24 1551 RI1FJL 9K2NO LL38 (x2) 164930 +6 1638 9K2NO OH3NXW KP11 165000 +4 701 9K2NO RA4FP +02 165000 -2 1764 9K2NO OH3NXW KP11 (x4) 170600 +5 1300 9K2NO R2SN KO94 (x4)
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