KN4IOG — reception at SO8OO
Signals decoded by SO8OO in southeastern Poland. FT8 and CW have separate histories; all times are UTC.
FT8 activity
Receiver-side FT8 activity involving KN4IOG, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-11-04.
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 KN4IOG as the transmitting token by decoded message structure across 1 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
- 1 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 KN4IOG in decoded directed-looking exchanges:
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 | KN4IOG S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 11-04 03:42 | 80m | - / -12 | OK2ZAW | +23 / - | 2 | ✓ Closing fragment |
| 11-04 03:06 | 80m | - / -16 | MI0NWA | +7 / - | 3 | ✓ Closing fragment |
| 11-04 02:50 | 80m | - / -11 | F1PBZ | +11 / - | 4 | ✓ Closing fragment |
| 11-04 02:50 | 80m | -18 / -13 | OM2WQ | +7 / -18 | 5 | ✓ Full exchange observed |
| 11-04 01:46 | 60m | - / -18 | F5RRS | -6 / - | 3 | ✓ Closing fragment |
| 11-04 01:16 | 60m | - / -20 | F5HNQ | +5 / - | 3 | ✓ Closing fragment |
| 09-28 03:36 | 80m | - / -18 | ON7GB | +7 / - | 6 | ✓ Closing fragment |
| 09-28 03:17 | 80m | - / - | ON7GB | +10 / - | 3 | Partial capture |
| 09-28 02:32 | 80m | - / -14 | EC3A | -12 / - | 3 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 025045 +6 2060 KN4IOG OM2WQ JN88 025045 +8 455 KN4IOG F1PBZ -11 025100 -18 1400 OM2WQ KN4IOG -18 025115 +7 2060 KN4IOG OM2WQ R-13 025115 +15 455 KN4IOG F1PBZ -11 025130 -19 1400 OM2WQ KN4IOG RR73 025145 +7 2060 KN4IOG OM2WQ 73 025145 +10 455 KN4IOG F1PBZ -11 (x2) 025330 -19 1400 EA1IOK KN4IOG RR73 030630 +5 732 KN4IOG MI0NWA -16 (x3) 034230 +24 425 KN4IOG OK2ZAW -12 (x2)
UTC dB Audio Message 011600 +5 2700 KN4IOG F5HNQ IN98 (x3) 014645 -4 1904 KN4IOG F5RRS JN36 (x3)
UTC dB Audio Message 001300 -6 1775 KN4IOG SV5BYP -12 (x2)
CW
No CW receptions recorded for this callsign in the last 30 days.
Explore CW reception at SO8OOFT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee