EA5AEP — FT8 activity observed at SO8OO

DXCC entity inferred from callsign: Spain Most frequent locator attributed to this token: IM98

Receiver-side FT8 activity involving EA5AEP, decoded by SO8OO in southeastern Poland. 9 FT8 messages attributed to this token as transmitter, on 20m, 10m, across 6 UTC dates in the available aggregate history. Observed between 2026-06-07 and 2026-06-28.

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

Overview

9
Messages attributed
6
UTC dates decoded
6
Active 15-min windows
-13 dB
Estimated median S/N

Bands

First attributed message: 2026-06-07
Last attributed message: 2026-06-28 19:06 UTC

Observed FT8 message patterns

Attributed sample
9 messages
Active dates
6 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) 4, 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 EA5AEP in decoded directed-looking exchanges:

Most frequent locator attributed to EA5AEP

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
IM98 · 5 decoded messages
SO8OO receiver locator
KN09VW
Locator-centre separation
2,203 km (approx.)
Last such locator decoded
2026-06-28 19:05 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 UTCBandEA5AEP S/NCounterpartCounterpart S/NMsgsCapture
07-02 11:03 10m - / - RW6HP -23 / - 2 Partial capture
06-28 19:05 10m -13 / - BH5HFK - / -14 3 ✓ Closing fragment

Recent FT8 messages decoded at SO8OO

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

10m
UTC    dB Audio  Message
190545 -13 1209  BH5HFK EA5AEP IM98 (x3)
110330 -24 1656  EA5AEP RW6HP LN14 (x2)
20m
UTC    dB Audio  Message
155830 -14  551  RI0SP EA5AEP R-08

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