R3QA — FT8 activity observed at SO8OO

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

Receiver-side FT8 activity involving R3QA, decoded by SO8OO in southeastern Poland. 7 FT8 messages attributed to this token as transmitter, on 160m, 80m, across 2 UTC dates in the available aggregate history. Observed between 2026-09-15 and 2026-09-21.

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 7 FT8 messages attributed to R3QA as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The largest monitored-band total was 80 m (57%), followed by 160 m (43%). In this small sample, the estimated median decoder S/N was -13 dB; no usual signal pattern is inferred.

Overview

Messages attributed

UTC dates decoded

Active 15-min windows

-13 dB

Estimated median S/N

Bands

160m · 3 80m · 4

First attributed message: 2026-09-15
Last attributed message: 2026-09-21 16:39 UTC

Observed FT8 message patterns

Attributed sample: 7 messages
Active dates: 2 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) 2, moderate (-15 to -9 dB) 2, strong (≥ -8 dB) 3.

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 R3QA

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: KO91 · 5 decoded messages
SO8OO receiver locator: KN09VW
Locator-centre separation: 1,221 km (approx.)
Last such locator decoded: 2026-09-21 16:39 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	R3QA S/N	Counterpart	Counterpart S/N	Msgs	Capture
09-21 16:38	160m	-17 / -	RI1FJZ	- / -	2	Partial capture
09-21 16:06	80m	0 / -	RI1FJZ	- / -11	3	Partial capture

Recent FT8 messages decoded at SO8OO

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

160m

UTC    dB Audio  Message
163445 -16 1830  RI1FJZ R3QA KO91 (x3)

80m

UTC    dB Audio  Message
170500 -15  402  RD0L R3QA R-10
160615  -5 1718  RI1FJZ R3QA KO91 (x3)

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