R6DX — FT8 activity observed at SO8OO

DXCC entity inferred from callsign: European Russia Most frequent locator attributed to this token: LN05

Receiver-side FT8 activity involving R6DX, decoded by SO8OO in southeastern Poland. 18 FT8 messages attributed to this token as transmitter, on 160m, 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-09-04.

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 18 FT8 messages attributed to R6DX 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 (61%), followed by 160 m (39%). In this small sample, the estimated median decoder S/N was -13 dB; no usual signal pattern is inferred.

Overview

18
Messages attributed
1
UTC dates decoded
2
Active 15-min windows
-13 dB
Estimated median S/N

Bands

First attributed message: 2026-09-04
Last attributed message: 2026-09-04 20:23 UTC

Observed FT8 message patterns

Attributed sample
18 messages
Active dates
1 UTC dates
Estimated median S/N
-13 dB
S/N percentile sample
Too small
Recurring-pattern threshold
Not met

SO8OO display ranges among successful decodes: weak (≤ -16 dB) 3, moderate (-15 to -9 dB) 11, strong (≥ -8 dB) 4.

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 R6DX in decoded directed-looking exchanges:

Most frequent locator attributed to R6DX

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
LN05 · 15 decoded messages
SO8OO receiver locator
KN09VW
Locator-centre separation
1,514 km (approx.)
Last such locator decoded
2026-09-04 20:22 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 UTCBandR6DX S/NCounterpartCounterpart S/NMsgsCapture
09-04 20:23 160m - / - RK4FD 0 / - 7 Partial capture
09-04 20:17 160m -16 / - RI1FJL - / -16 7 ✓ Closing fragment
09-04 20:14 80m -10 / - RI1FJL - / -22 7 Partial capture
09-04 20:08 80m -9 / - RI1FJL - / - 4 Partial capture

Recent FT8 messages decoded at SO8OO

Frequency values are decoder audio offsets in hertz, not RF frequencies.

160m
UTC    dB Audio  Message
201715 -13  897  RI1FJL R6DX LN05 (x7)
202330  +1 1380  R6DX RK4FD LO22 (x7)
80m
UTC    dB Audio  Message
200830 -13  537  RI1FJL R6DX LN05 (x11)

FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee