UY5TE — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving UY5TE, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 20m, 10m, across 3 UTC dates in the available aggregate history. Observed between 2026-06-13 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 4 FT8 messages attributed to UY5TE as the transmitting token by decoded message structure across 3 UTC dates in the available aggregate history. The available sample contains attributed decodes on 20 m (50%) and 10 m (50%). The sample is too small to infer a recurring UTC-hour or received-S/N pattern.
Overview
Bands
Last attributed message: 2026-08-25 07:09 UTC
Observed FT8 message patterns
- Attributed sample
- 4 messages
- Active dates
- 3 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 UY5TE in decoded directed-looking exchanges:
Most frequent locator attributed to UY5TE
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
- KN56 · 4 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 781 km (approx.)
- Last such locator decoded
- 2026-08-25 07:09 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 | UY5TE S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-26 15:12 | 20m | - / -13 | UN7PNF | -7 / - | 3 | ✓ Closing fragment |
| 08-25 07:13 | 20m | - / -14 | DB7GE | -1 / - | 6 | ✓ Closing fragment |
| 08-24 07:22 | 20m | - / -7 | HB9CXZ | +12 / - | 2 | ✓ Closing fragment |
| 08-24 07:19 | 20m | - / -13 | DJ3HW | +12 / - | 3 | ✓ Closing fragment |
| 07-24 07:07 | 20m | - / -9 | Z62NS | -16 / - | 3 | ✓ Closing fragment |
| 06-25 09:13 | 20m | - / -20 | YO6OGW | -6 / - | 2 | ✓ Closing fragment |
| 06-25 07:37 | 20m | - / -10 | SV2AOB | -20 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 072000 +13 1256 UY5TE DJ3HW RR73 072215 +9 2018 UY5TE HB9CXZ -07 (x2) 075215 -5 1819 UY5TE DL2FK -19 070930 -10 343 DB7GE UY5TE KN56 071330 +1 2079 UY5TE DB7GE -14 (x6) 072130 +8 1975 UY5TE S51CE -13 151200 -3 2014 UY5TE UN7PNF -13 (x3)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee