HB9DUT — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving HB9DUT, decoded by SO8OO in southeastern Poland. 1 FT8 messages attributed to this token as transmitter, on 20m, across 1 UTC dates in the available aggregate history. Last observed 2026-07-23.
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 1 FT8 messages attributed to HB9DUT 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
- 1 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 HB9DUT in decoded directed-looking exchanges:
Most frequent locator attributed to HB9DUT
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
- JN36
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,158 km (approx.)
- Last such locator decoded
- 2026-07-23 13:49 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 | HB9DUT S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 07-26 12:05 | 20m | - / -11 | DG1KFR | -21 / - | 2 | Partial capture |
| 07-23 13:17 | 20m | - / -18 | OZ9FF | -16 / - | 2 | ✓ Closing fragment |
| 07-23 12:25 | 20m | - / -15 | DK3HV | -12 / - | 2 | ✓ Closing fragment |
| 07-23 12:23 | 20m | - / -8 | TK5K | -8 / - | 3 | ✓ Closing fragment |
| 07-23 12:13 | 20m | - / - | DL3JAC | -14 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 122330 -11 532 HB9DUT TK5K -08 (x3) 122530 -14 1207 HB9DUT DK3HV R-15 (x2) 122930 -16 2245 HB9DUT SV1CQN -10 131745 -17 2324 HB9DUT OZ9FF -18 (x2) 133115 -21 1420 HB9DUT R4LBP RR73 134315 -15 913 HB9DUT CT1EDA -15 134930 -22 1207 PD4RJ HB9DUT JN36 143400 -12 2170 HB9DUT SV5AZK -14 143900 -21 1241 HB9DUT ON8PB -03 120545 -20 1920 HB9DUT DG1KFR -11 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee