KA3EHL — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving KA3EHL, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-17 and 2026-06-18.
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 2 FT8 messages attributed to KA3EHL 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
- 2 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 KA3EHL in decoded directed-looking exchanges:
Most frequent locator attributed to KA3EHL
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
- EM90
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 8,294 km (approx.)
- Last such locator decoded
- 2026-06-17 23:52 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 | KA3EHL S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-15 00:15 | 40m | - / -4 | KN6RO | -12 / - | 2 | ✓ Closing fragment |
| 09-09 23:14 | 40m | - / -11 | EA5JLN | -16 / - | 2 | Partial capture |
| 09-01 00:01 | 40m | - / -1 | W5J | -24 / - | 2 | ✓ Closing fragment |
| 08-31 02:06 | 80m | - / - | F4UJU | -2 / - | 3 | Partial capture |
| 08-31 02:05 | 80m | - / - | F4BYA | +1 / - | 3 | Partial capture |
| 08-31 01:57 | 80m | - / - | F4BYA | -6 / - | 3 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 014445 -1 2875 KA3EHL F4FPR IN88 234715 -19 2441 KA3EHL AD4K FM08 000100 -23 1902 KA3EHL W5J -01 (x2) 231400 -14 1737 KA3EHL EA5JLN -11 (x2) 001530 -12 942 KA3EHL KN6RO -04 (x2) 000300 -13 2351 KA3EHL MI7XHT IO64 (x2)
UTC dB Audio Message 015730 -5 2809 KA3EHL F4BYA JN19 (x5) 020630 -4 1246 KA3EHL F4UJU JN06 020630 +0 2809 KA3EHL F4BYA JN19 020700 +0 1247 KA3EHL F4UJU JN06 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee