SP7EXY — FT8 activity observed at SO8OO

DXCC entity inferred from callsign: Poland Most frequent locator attributed to this token: KO00

Receiver-side FT8 activity involving SP7EXY, decoded by SO8OO in southeastern Poland. 5 FT8 messages attributed to this token as transmitter, on 10m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-10 and 2026-06-14.

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 SP7EXY as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The largest monitored-band total was 10 m (100%). In this small sample, the estimated median decoder S/N was -20 dB; no usual signal pattern is inferred.

Overview

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

Bands

First attributed message: 2026-06-10
Last attributed message: 2026-06-14 09:13 UTC

Observed FT8 message patterns

Attributed sample
5 messages
Active dates
2 UTC dates
Estimated median S/N
-20 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) 1, 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).

Frequent counterpart tokens observed at SO8OO

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

Most frequent locator attributed to SP7EXY

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
KO00 · 2 decoded messages
SO8OO receiver locator
KN09VW
Locator-centre separation
84 km (approx.)
Last such locator decoded
2026-06-10 13:23 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 UTCBandSP7EXY S/NCounterpartCounterpart S/NMsgsCapture
08-27 11:19 10m - / - DL3NGN -17 / - 3 ✓ Closing fragment
08-27 11:19 10m - / -16 F4AYI -18 / - 2 Partial capture
08-27 11:17 10m - / -16 CR7BRV +5 / - 2 ✓ Closing fragment
08-27 10:47 10m - / - F4LSL -5 / - 2 Partial capture
08-17 08:32 10m - / 0 F5CUN +1 / - 4 ✓ Closing fragment

Recent FT8 messages decoded at SO8OO

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

10m
UTC    dB Audio  Message
083245  +3  483  SP7EXY F5CUN JN26 (x4)
104730  -5 2195  SP7EXY F4LSL JN36 (x2)
111745  +5  666  SP7EXY CR7BRV R-16 (x2)
111945 -19 2321  SP7EXY F4AYI JN08
111945 -17 1180  SP7EXY DL3NGN JN59 (x2)
112045 -17 2321  SP7EXY F4AYI R-16
112045 -18 1180  SP7EXY DL3NGN 73

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