EA1HS — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving EA1HS, 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-07-09.
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 EA1HS 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 EA1HS in decoded directed-looking exchanges:
Most frequent locator attributed to EA1HS
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 · 2 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 2,067 km (approx.)
- Last such locator decoded
- 2026-07-09 16: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 UTC | Band | EA1HS S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-19 19:26 | 60m | - / -13 | EA9UV | -14 / - | 2 | ✓ Closing fragment |
| 07-18 17:01 | 10m | - / -11 | UV3IP | -13 / - | 3 | ✓ Closing fragment |
| 07-09 16:23 | 20m | - / - | PD3LKN | -15 / - | 4 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 192615 -12 788 EA1HS EA9UV -13 (x2)
UTC dB Audio Message 170100 -15 2022 EA1HS YO9PH -04 170130 -14 1195 EA1HS UV3IP KN88 170130 -3 2698 EA1HS IQ4JO JN63 170200 -10 1195 EA1HS UV3IP R-11 (x2)
UTC dB Audio Message 162245 -7 1076 CQ EA1HS IN82 162300 -15 1075 EA1HS PD3LKN JO22 162315 -6 1076 CQ EA1HS IN82 162330 -15 1075 EA1HS PD3LKN JO22 (x3)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee