LU2DAJ — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving LU2DAJ, decoded by SO8OO in southeastern Poland. 1 FT8 messages attributed to this token as transmitter, on 10m, across 1 UTC dates in the available aggregate history. Last observed 2026-06-28.
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 LU2DAJ as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The available sample contains attributed decodes on 10 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 LU2DAJ in decoded directed-looking exchanges:
Most frequent locator attributed to LU2DAJ
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
- GF05
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 12,276 km (approx.)
- Last such locator decoded
- 2026-06-28 20:32 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 | LU2DAJ S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 07-20 19:25 | 10m | - / -4 | ON3MV | -16 / - | 4 | Partial capture |
| 07-17 18:54 | 10m | - / -7 | RW4M | -18 / - | 3 | ✓ Closing fragment |
| 07-17 18:41 | 10m | - / -19 | IW2HUS | -13 / - | 3 | ✓ Closing fragment |
| 06-28 20:31 | 10m | -13 / -13 | F4DUZ | -11 / - | 13 | ✓ Closing observed |
| 06-28 20:26 | 10m | - / -12 | UA4FOH | -8 / - | 2 | ✓ Closing fragment |
| 06-28 20:20 | 10m | - / -9 | IK2VFR | -2 / - | 5 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 203645 -16 985 LU2DAJ F4DUZ RR73 (x3) 205330 -20 1868 LU2DAJ DO6LE RR73 184100 -11 1080 LU2DAJ IW2HUS -19 (x3) 185445 -18 1346 LU2DAJ RW4M LO44 (x3) 192545 -19 2002 LU2DAJ ON3MV JO21 (x4) 161915 -23 1709 LU2DAJ A61FJ -12
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee