UR3AIO — FT8 activity observed at SO8OO

DXCC entity inferred from callsign: Ukraine Most frequent locator attributed to this token: KO70

Receiver-side FT8 activity involving UR3AIO, 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-06-10.

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 UR3AIO 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 -7 dB; no usual signal pattern is inferred.

Overview

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

Bands

First attributed message: 2026-06-10
Last attributed message: 2026-06-10 06:46 UTC

Observed FT8 message patterns

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

SO8OO display ranges among successful decodes: weak (≤ -16 dB) 0, 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).

Frequent counterpart tokens observed at SO8OO

Tokens most often paired with UR3AIO in decoded directed-looking exchanges:

Most frequent locator attributed to UR3AIO

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
KO70 · 5 decoded messages
SO8OO receiver locator
KN09VW
Locator-centre separation
941 km (approx.)
Last such locator decoded
2026-06-10 06:46 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 UTCBandUR3AIO S/NCounterpartCounterpart S/NMsgsCapture
09-02 18:52 80m - / -15 UV1IX +3 / - 3 ✓ Closing fragment
07-17 18:36 40m - / -12 SQ5WBW/P -8 / - 2 ✓ Closing fragment
07-17 17:52 20m - / -5 JY5CG -12 / - 2 ✓ Closing fragment

Recent FT8 messages decoded at SO8OO

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

80m
UTC    dB Audio  Message
185230  +5 1575  UR3AIO UV1IX KN88 (x3)
40m
UTC    dB Audio  Message
183645  -8  377  UR3AIO SQ5WBW/P -12 (x2)
20m
UTC    dB Audio  Message
175230 -11 1563  UR3AIO JY5CG -05 (x2)

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