LU2CPO — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving LU2CPO, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-08-19 and 2026-08-25.
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 LU2CPO as the transmitting token by decoded message structure across 2 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
- 2 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 LU2CPO 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 | LU2CPO S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-28 04:15 | 20m | - / -26 | XQ1KK | -9 / - | 3 | Partial capture |
| 08-25 21:40 | 20m | -10 / -13 | LU1FIV | +2 / -16 | 4 | ✓ Full exchange observed |
| 08-19 15:10 | 10m | - / -18 | F4FSY | -16 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 233230 -17 827 J68TT LU2CPO -07 214030 -9 2704 LU1FIV LU2CPO -16 214045 +2 2704 LU2CPO LU1FIV R-13 214100 -11 2705 LU1FIV LU2CPO RR73 214115 +2 2705 LU2CPO LU1FIV 73 041530 -9 1486 LU2CPO XQ1KK R-26 (x3)
UTC dB Audio Message 151045 -17 1463 LU2CPO F4FSY -18 (x2)
Decoder S/N history by band
Count-weighted daily averages across messages attributed to this profiled token and successfully decoded at SO8OO, limited to the rolling 90-day UTC chart window.
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee