KM4JOK — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving KM4JOK, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-09-08.
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 4 FT8 messages attributed to KM4JOK 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
- 4 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 KM4JOK in decoded directed-looking exchanges:
Most frequent locator attributed to KM4JOK
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
- EM95
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 7,876 km (approx.)
- Last such locator decoded
- 2026-09-08 01:53 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 | KM4JOK S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-08 01:53 | 80m | -13 / - | W4WHQ | - / - | 2 | Partial capture |
| 09-08 01:52 | 80m | - / - | R6OAF | +2 / - | 2 | Partial capture |
| 09-08 01:49 | 80m | -16 / - | N8BV | - / +1 | 2 | ✓ Closing fragment |
| 09-08 01:47 | 80m | - / -18 | DK7ZT | +13 / - | 5 | Partial capture |
| 09-08 01:46 | 80m | - / -7 | ON1JP | -11 / - | 5 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 014745 -11 1567 KM4JOK ON1JP -07 014745 +14 1115 KM4JOK DK7ZT -18 014815 -7 1567 KM4JOK ON1JP -07 014815 +16 1115 KM4JOK DK7ZT -18 014845 -9 1567 KM4JOK ON1JP -07 014845 +14 1115 KM4JOK DK7ZT -18 014915 -16 1484 N8BV KM4JOK R+01 014915 +12 1115 KM4JOK DK7ZT -18 014945 -17 1484 N8BV KM4JOK 73 015215 +4 1831 KM4JOK R6OAF KN88 (x2) 015330 +1 1484 KM4JOK US2YW KN28 015330 -7 781 KM4JOK OE3OOG JN87 015345 -12 1483 W4WHQ KM4JOK EM95 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee