PY3CNN — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving PY3CNN, decoded by SO8OO in southeastern Poland. 8 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 8 FT8 messages attributed to PY3CNN as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The largest monitored-band total was 10 m (100%). In this small sample, the estimated median decoder S/N was -21 dB; no usual signal pattern is inferred.
Overview
Observed FT8 message patterns
- Attributed sample
- 8 messages
- Active dates
- 1 UTC dates
- Estimated median S/N
- -21 dB
- S/N percentile sample
- Too small
- Recurring-pattern threshold
- Not met
SO8OO display ranges among successful decodes: weak (≤ -16 dB) 8, moderate (-15 to -9 dB) 0, strong (≥ -8 dB) 0.
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 PY3CNN in decoded directed-looking exchanges:
Most frequent locator attributed to PY3CNN
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
- GF38 · 6 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 11,656 km (approx.)
- Last such locator decoded
- 2026-06-07 19:15 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 | PY3CNN S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-30 19:50 | 20m | - / -24 | US5HL | +1 / - | 2 | ✓ Closing fragment |
| 08-22 18:05 | 10m | - / -14 | PF7DKW | -23 / - | 2 | ✓ Closing fragment |
| 08-21 19:26 | 10m | - / -13 | PD4DX | -10 / - | 2 | Partial capture |
| 07-29 19:00 | 10m | - / -17 | IU8ADS | -8 / - | 7 | Partial capture |
| 07-29 18:54 | 10m | - / -13 | S59MA | -16 / - | 6 | Partial capture |
| 07-28 19:34 | 10m | - / -5 | ON6AA | -11 / - | 2 | Partial capture |
| 07-15 20:15 | 20m | - / -15 | UN0GY | -9 / - | 3 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 201545 -8 2369 PY3CNN UN0GY -15 (x3) 195015 +1 2963 PY3CNN US5HL -24 (x2)
UTC dB Audio Message 185530 -17 1778 PY3CNN S59MA JN76 (x3) 190000 -9 1834 PY3CNN IU8ADS JN70 (x7) 192600 -8 1634 PY3CNN PD4DX JO33 (x2) 202930 -9 2303 PY3CNN G1OZO R-07 180530 -24 1585 PY3CNN PF7DKW -14 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee