DA1DO — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving DA1DO, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 20m, across 1 UTC dates in the available aggregate history. Last observed 2026-08-16.
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 3 FT8 messages attributed to DA1DO 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
- 3 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 DA1DO in decoded directed-looking exchanges:
Most frequent locator attributed to DA1DO
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
- JO40
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 911 km (approx.)
- Last such locator decoded
- 2026-08-16 10:36 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 | DA1DO S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-16 10:58 | 20m | - / -6 | OH6GAZ | -22 / - | 2 | ✓ Closing fragment |
| 08-16 10:57 | 20m | - / -7 | OE4RGC | -14 / - | 2 | Partial capture |
| 08-16 10:42 | 20m | -24 / - | R5AV | -18 / -11 | 2 | ✓ Closing observed |
| 07-11 14:01 | 20m | - / -11 | TM40TFR | +8 / - | 5 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 140130 +5 2645 DA1DO TM40TFR -11 (x5) 103645 -24 1870 ZB2LGT DA1DO JO40 104015 -24 1869 OE8PIT DA1DO -13 104245 -24 1869 R5AV DA1DO R-11 104300 -18 1870 DA1DO R5AV RR73 105730 -11 2391 DA1DO OE4RGC JN87 105800 -20 1868 DA1DO OH6GAZ -06 (x2) 105930 -16 2391 DA1DO OE4RGC R-07
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee