HB9DSL — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving HB9DSL, decoded by SO8OO in southeastern Poland. 5 FT8 messages attributed to this token as transmitter, on 40m, across 1 UTC dates in the available aggregate history. Last observed 2026-09-01.
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 5 FT8 messages attributed to HB9DSL as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The largest monitored-band total was 40 m (100%). In this small sample, the estimated median decoder S/N was +1 dB; no usual signal pattern is inferred.
Overview
Observed FT8 message patterns
- Attributed sample
- 5 messages
- Active dates
- 1 UTC dates
- Estimated median S/N
- +1 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) 0, strong (≥ -8 dB) 5.
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 HB9DSL in decoded directed-looking exchanges:
Most frequent locator attributed to HB9DSL
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
- JN37
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,116 km (approx.)
- Last such locator decoded
- 2026-09-01 19:37 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 | HB9DSL S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-01 19:40 | 40m | - / +3 | ON5LC | -8 / - | 3 | Partial capture |
| 09-01 19:37 | 40m | -1 / -15 | F1PBZ | -10 / -8 | 5 | ✓ Full exchange observed |
| 09-01 19:36 | 40m | +1 / -7 | SQ4FDK | -8 / -13 | 3 | ✓ Full exchange observed |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 193600 +1 813 SQ4FDK HB9DSL -13 193615 -9 1001 HB9DSL SQ4FDK R-07 (x2) 193700 +2 814 CQ HB9DSL JN37 193715 -12 2288 HB9DSL F1PBZ -15 193730 -2 814 F1PBZ HB9DSL R-08 193745 -8 2288 HB9DSL F1PBZ RR73 193800 -1 814 F1PBZ HB9DSL R-08 (x2) 194045 -8 814 HB9DSL ON5LC JO20 (x3)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee