RY4ABF — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving RY4ABF, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 40m, across 1 UTC dates in the available aggregate history. Last observed 2026-10-02.
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 RY4ABF as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The available sample contains attributed decodes on 40 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
- 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).
Most frequent locator attributed to RY4ABF
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
- LN28
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,686 km (approx.)
- Last such locator decoded
- 2026-10-02 15: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 | RY4ABF S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 10-02 15:54 | 40m | - / - | SP6FME | 0 / - | 3 | Partial capture |
| 10-02 15:53 | 40m | +2 / - | F4MXT/P | - / -4 | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 155315 +2 611 F4MXT/P RY4ABF LN28 (x2) 155430 +2 610 RY4ABF SP6FME JO90 (x3)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee