YU4RDX — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving YU4RDX, decoded by SO8OO in southeastern Poland. 5 FT8 messages attributed to this token as transmitter, on 20m, across 1 UTC dates in the available aggregate history. Last observed 2026-07-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 5 FT8 messages attributed to YU4RDX as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The largest monitored-band total was 20 m (100%). In this small sample, the estimated median decoder S/N was -16 dB; no usual signal pattern is inferred.
Overview
Observed FT8 message patterns
- Attributed sample
- 5 messages
- Active dates
- 1 UTC dates
- Estimated median S/N
- -16 dB
- S/N percentile sample
- Too small
- Recurring-pattern threshold
- Not met
SO8OO display ranges among successful decodes: weak (≤ -16 dB) 4, moderate (-15 to -9 dB) 1, strong (≥ -8 dB) 0.
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 YU4RDX in decoded directed-looking exchanges:
Most frequent locator attributed to YU4RDX
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
- JN94 · 3 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 640 km (approx.)
- Last such locator decoded
- 2026-07-18 15:02 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 | YU4RDX S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-01 15:27 | 20m | - / +6 | R2AL | -8 / - | 2 | Partial capture |
| 07-18 15:01 | 20m | -16 / - | YI1QEA | - / - | 3 | Partial capture |
| 07-18 15:00 | 20m | -16 / - | OE8XRK | -11 / - | 2 | ✓ Closing observed |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 145745 -13 1026 OY1R YU4RDX R-15 150045 -16 1027 OE8XRK YU4RDX RR73 150100 -11 1027 YU4RDX OE8XRK 73 150115 -16 1027 YI1QEA YU4RDX JN94 (x3) 152715 -14 762 YU4RDX R2AL KO85 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee