LU3DOY — reception at SO8OO
Signals decoded by SO8OO in southeastern Poland. FT8 and CW have separate histories; all times are UTC.
FT8 activity
Receiver-side FT8 activity involving LU3DOY, 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-07.
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 LU3DOY 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 LU3DOY in decoded directed-looking exchanges:
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 | LU3DOY S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 11-01 14:19 | 10m | - / -22 | F1PBZ | 0 / - | 4 | Partial capture |
| 09-19 18:18 | 10m | - / - | SQ8SBP | -18 / - | 2 | Partial capture |
| 08-23 14:07 | 10m | - / -17 | F5UOU | -19 / - | 3 | Partial capture |
| 08-17 18:35 | 10m | - / -20 | R7OQ | -14 / - | 3 | ✓ Closing fragment |
| 08-16 18:56 | 10m | - / -17 | RU3OZ | -4 / - | 4 | ✓ Closing fragment |
| 08-16 18:06 | 10m | - / -22 | UT6LX | -11 / - | 2 | Partial capture |
| 08-16 17:41 | 10m | - / -15 | UX3HX | -23 / - | 2 | Partial capture |
| 08-16 17:39 | 10m | - / -9 | UX1AA | -18 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 172730 -22 1943 LU3DOY RA4HLK LO53 183500 -14 1451 LU3DOY R7OQ -20 (x3) 140745 -21 1518 LU3DOY F5UOU -17 (x4) 181830 -19 1487 LU3DOY SQ8SBP KN19 (x2) 175445 -16 2495 LU3DOY F1PBZ -08 (x5)
CW
No CW receptions recorded for this callsign in the last 30 days.
Explore CW reception at SO8OOFT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee