R6DYY — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving R6DYY, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 10m, across 2 UTC dates in the available aggregate history. Observed between 2026-07-13 and 2026-07-23.
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 R6DYY as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The available sample contains attributed decodes on 10 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 R6DYY 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 | R6DYY S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-11 08:03 | 10m | - / -2 | RK4FD | -8 / - | 2 | Partial capture |
| 07-23 14:32 | 10m | - / -9 | R2EA | -6 / - | 2 | ✓ Closing fragment |
| 07-17 07:56 | 10m | - / -14 | IU5NRS | -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 082115 -24 1954 SP5PDA R6DYY R-06 075630 -3 1169 R6DYY IU5NRS -14 (x2) 143245 -5 2567 R6DYY R2EA -09 (x2) 143630 -17 1782 R7TO R6DYY RR73 143715 -24 1395 R6DYY RA3VX -03 080330 -8 1181 R6DYY RK4FD LO22 (x2)
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.
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee