RD6AY — 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 RD6AY, decoded by SO8OO in southeastern Poland. 6 FT8 messages attributed to this token as transmitter, on 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-11-03.
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 6 FT8 messages attributed to RD6AY as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The largest monitored-band total was 80 m (100%). In this small sample, the estimated median decoder S/N was -23 dB; no usual signal pattern is inferred.
Overview
Observed FT8 message patterns
- Attributed sample
- 6 messages
- Active dates
- 1 UTC dates
- Estimated median S/N
- -23 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) 2, 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).
Most frequent locator attributed to RD6AY
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
- LN12 · 2 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,821 km (approx.)
- Last such locator decoded
- 2026-11-03 00:10 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 | RD6AY S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 11-03 00:11 | 80m | - / -17 | EK/RX3DPK | -7 / - | 2 | Partial capture |
| 11-03 00:11 | 80m | -16 / -25 | GI4SNA | +8 / -19 | 4 | Partial capture |
| 11-03 00:10 | 80m | -20 / - | OZ2JFS/P | - / -18 | 2 | Partial capture |
| 11-03 00:10 | 80m | -18 / - | UA9XL/P | - / -13 | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 001015 -24 1853 UA9XL/P RD6AY LN12 001045 -24 1768 OZ2JFS/P RD6AY LN12 001100 +7 1079 RD6AY GI4SNA -25 001100 -9 2654 RD6AY EK/RX3DPK -17 001115 -16 1768 OZ2JFS/P RD6AY R-18 001130 -11 1661 RD6AY RA9UUG NO34 001130 +10 1079 RD6AY GI4SNA -25 001130 -5 2654 RD6AY EK/RX3DPK -17 001215 -11 2563 UA9XL/P RD6AY R-13 001245 -10 2562 GI4SNA RD6AY R-19 (x2)
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