2E0ACE — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving 2E0ACE, decoded by SO8OO in southeastern Poland. 6 FT8 messages attributed to this token as transmitter, on 20m, across 3 UTC dates in the available aggregate history. Observed between 2026-08-24 and 2026-08-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 6 FT8 messages attributed to 2E0ACE as the transmitting token by decoded message structure across 3 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 -10 dB; no usual signal pattern is inferred.
Overview
Observed FT8 message patterns
- Attributed sample
- 6 messages
- Active dates
- 3 UTC dates
- Estimated median S/N
- -10 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) 3, 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 2E0ACE in decoded directed-looking exchanges:
Most frequent locator attributed to 2E0ACE
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
- IO84 · 5 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,753 km (approx.)
- Last such locator decoded
- 2026-08-26 05: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 UTC | Band | 2E0ACE S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-24 17:02 | 20m | -6 / - | UN0GY | - / - | 3 | Partial capture |
| 08-15 17:17 | 40m | - / -9 | PE9JAN | -21 / - | 3 | ✓ Closing fragment |
| 07-31 19:46 | 20m | - / -12 | TN8GD | -7 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 194600 -5 601 2E0ACE TN8GD -12 (x2) 170245 -6 362 UN0GY 2E0ACE IO84 (x4) 052200 -12 1124 XQ1KK 2E0ACE IO84 144130 -14 1120 UN7PNF 2E0ACE 73 163545 -14 2084 2E0ACE UN3P -17
UTC dB Audio Message 171745 -21 1736 2E0ACE PE9JAN JO22 (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