PY2HX — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving PY2HX, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 10m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-21 and 2026-06-26.
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 PY2HX as the transmitting token by decoded message structure across 2 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
- 4 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 PY2HX in decoded directed-looking exchanges:
Most frequent locator attributed to PY2HX
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
- GG58 · 3 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 10,540 km (approx.)
- Last such locator decoded
- 2026-06-21 19:00 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 | PY2HX S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-22 18:39 | 10m | - / -3 | UX3HX | -17 / - | 11 | ✓ Closing fragment |
| 08-22 17:57 | 10m | - / -7 | DL1TS | -14 / - | 3 | ✓ Closing fragment |
| 08-22 17:57 | 10m | - / - | RD7KW | +9 / - | 4 | Partial capture |
| 08-21 14:12 | 10m | - / -18 | LZ2VQ | -8 / - | 2 | Partial capture |
| 08-20 21:20 | 20m | - / -18 | DL6KA | -2 / - | 6 | Partial capture |
| 07-25 21:15 | 20m | - / -1 | DH1JG | -15 / - | 15 | Partial capture |
| 06-26 20:49 | 10m | - / - | RK6OV | -22 / - | 3 | Partial capture |
| 06-26 18:09 | 10m | - / -11 | UA4AGU | -11 / - | 5 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 175830 +5 2847 PY2HX RD7KW KN75 175830 -15 1582 PY2HX DL1TS 73 175900 +9 2847 PY2HX RD7KW KN75 183830 -19 2380 PY2HX PD2FS -15 183900 -14 1255 PY2HX UX3HX KN79 (x11)
UTC dB Audio Message 211845 -15 1232 PY2HX DH1JG JO31 (x9) 212030 -4 596 PY2HX DL6KA -18 (x6)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee