EA1FT — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving EA1FT, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 20m, across 1 UTC dates in the available aggregate history. Last observed 2026-08-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 2 FT8 messages attributed to EA1FT as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The available sample contains attributed decodes on 20 m (100%). The sample is too small to infer a recurring UTC-hour or received-S/N pattern.
Overview
Observed FT8 message patterns
- Attributed sample
- 2 messages
- Active dates
- 1 UTC dates
- S/N summary
- Too few decodes
- S/N percentile sample
- Too small
- Recurring-pattern threshold
- Not met
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 EA1FT in decoded directed-looking exchanges:
Most frequent locator attributed to EA1FT
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
- IN82
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 2,067 km (approx.)
- Last such locator decoded
- 2026-08-14 06:44 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 | EA1FT S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-11 07:45 | 40m | - / -24 | F5RRS | -3 / - | 5 | ✓ Closing fragment |
| 09-04 02:37 | 40m | - / -13 | UA6LET | +2 / - | 2 | ✓ Closing fragment |
| 09-04 02:21 | 40m | - / -12 | PC2J | -2 / - | 5 | ✓ Closing fragment |
| 08-14 06:48 | 20m | - / +1 | IK4LZH | -12 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 022130 -2 856 EA1FT PC2J JO22 (x5) 022500 -15 1397 EA1FT ON1DGN -05 023700 +1 557 EA1FT UA6LET -13 (x2) 074545 -1 743 EA1FT F5RRS JN36 (x5)
UTC dB Audio Message 184700 -21 2166 EA1FT PY5BH -04
UTC dB Audio Message 064400 -20 1498 CQ EA1FT IN82 064430 -24 1497 RN6MA EA1FT R+06 064845 -13 463 EA1FT IK4LZH JN54 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee