UA6LIY — 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 UA6LIY, decoded by SO8OO in southeastern Poland. 12 FT8 messages attributed to this token as transmitter, on 160m, across 2 UTC dates in the available aggregate history. Observed between 2026-08-30 and 2026-11-08.
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 12 FT8 messages attributed to UA6LIY as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The largest monitored-band total was 160 m (100%). In this small sample, the estimated median decoder S/N was -3 dB; no usual signal pattern is inferred.
Overview
Observed FT8 message patterns
- Attributed sample
- 12 messages
- Active dates
- 2 UTC dates
- Estimated median S/N
- -3 dB
- S/N percentile sample
- Too small
- Recurring-pattern threshold
- Not met
SO8OO display ranges among successful decodes: weak (≤ -16 dB) 0, moderate (-15 to -9 dB) 2, strong (≥ -8 dB) 10.
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).
Most frequent locator attributed to UA6LIY
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
- KN96 · 12 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,328 km (approx.)
- Last such locator decoded
- 2026-11-08 14:13 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 | UA6LIY S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 11-08 14:14 | 160m | - / - | RA3LCX | -17 / - | 4 | Partial capture |
| 11-08 14:12 | 160m | -11 / - | 5W1SA | - / - | 2 | Partial capture |
| 08-30 21:54 | 160m | -1 / - | RI1FJL | - / - | 9 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 215500 -6 2165 UA6LIY R5BM +04 215515 -3 1715 RI1FJL UA6LIY KN96 (x8) 141245 -10 1989 5W1SA UA6LIY KN96 (x2) 141400 -19 1240 UA6LIY RA3LCX KO65 (x4)
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.
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