HA5AGP — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving HA5AGP, 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-06-25.
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 HA5AGP 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 HA5AGP in decoded directed-looking exchanges:
Most frequent locator attributed to HA5AGP
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
- JN97
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 340 km (approx.)
- Last such locator decoded
- 2026-06-25 13:56 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 | HA5AGP S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-06 05:27 | 20m | - / -5 | TA6B | -4 / - | 2 | ✓ Closing fragment |
| 07-03 04:29 | 20m | - / - | EA1FAC | -7 / - | 2 | Partial capture |
| 06-30 06:07 | 20m | - / 0 | F5IXN | -2 / - | 4 | ✓ Closing fragment |
| 06-30 05:36 | 20m | - / -6 | SV8/UR4LBR | -8 / - | 2 | ✓ Closing fragment |
| 06-30 05:33 | 20m | - / -7 | 5B4ASY | -10 / - | 3 | ✓ Closing fragment |
| 06-30 05:26 | 20m | - / - | K2TQC | -18 / - | 2 | ✓ Closing fragment |
| 06-30 05:18 | 20m | - / -14 | TM8WWA | -14 / - | 2 | Partial capture |
| 06-25 13:39 | 20m | -1 / +3 | SP1TMH | -12 / -3 | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 055930 -10 1757 HA5AGP GB2WWA -11 060030 -2 1757 HA5AGP RR73; OE6JFG <...> -18 060715 -2 1280 HA5AGP F5IXN JN23 (x4) 042130 -22 1302 HA5AGP RY4D +05 042915 -10 963 HA5AGP EA1FAC RRR (x2) 104930 -14 1968 HA5AGP YO9PH -01 041430 -21 1921 HA5AGP RK9UE RR73 045445 -13 1655 HA5AGP N8HRZ -11 050745 -22 1607 HA5AGP UB6C -08 052730 -6 669 HA5AGP TA6B -05 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee