F4AKH — 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 F4AKH, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 80m, 40m, across 2 UTC dates in the available aggregate history. Observed between 2026-10-29 and 2026-10-30.
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 F4AKH 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 (67%) and 40 m (33%). The sample is too small to infer a recurring UTC-hour or received-S/N pattern.
Overview
Bands
Last attributed message: 2026-10-30 17:05 UTC
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 F4AKH 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 | F4AKH S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 10-30 17:05 | 80m | -22 / - | DO1FOX | -6 / -13 | 3 | ✓ Closing observed |
| 10-29 14:22 | 40m | - / - | DH2NJS | -10 / - | 6 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 142115 -24 2140 GM0KMJ F4AKH 73 142200 -10 2140 F4AKH DH2NJS JO50 (x6) 230630 +2 442 F4AKH CT7BRV -11 (x2)
UTC dB Audio Message 100730 -11 684 F4AKH RR73; PD7JLP <...> +16
UTC dB Audio Message 170515 -21 2106 DO1FOX F4AKH R-13 170530 -6 670 F4AKH DO1FOX RR73 170545 -22 2106 DO1FOX F4AKH 73
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.
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