PY2NSA — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving PY2NSA, decoded by SO8OO in southeastern Poland. 1 FT8 messages attributed to this token as transmitter, on 10m, across 1 UTC dates in the available aggregate history. Last observed 2026-06-20.
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 1 FT8 messages attributed to PY2NSA as the transmitting token by decoded message structure across 1 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
- 1 messages
- Active dates
- 1 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 PY2NSA in decoded directed-looking exchanges:
Most frequent locator attributed to PY2NSA
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
- GG67
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 10,504 km (approx.)
- Last such locator decoded
- 2026-06-20 15:43 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 | PY2NSA S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-18 23:41 | 40m | - / - | F5NBU | +6 / - | 4 | Partial capture |
| 08-18 20:56 | 40m | - / - | F5NBU | -1 / - | 3 | Partial capture |
| 07-07 19:11 | 10m | - / -13 | F1PBZ | -3 / - | 4 | Partial capture |
| 06-28 19:30 | 10m | - / -4 | EA8UP | -16 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 192800 -10 1729 PY2NSA HB9TMW 73 193030 -15 1776 PY2NSA EA8UP R-04 (x2) 191115 -9 2386 PY2NSA F1PBZ -13 (x4) 160045 -14 2002 PY2NSA <...> R-14 193815 -18 1315 PY2NSA PA8R 73
UTC dB Audio Message 205615 -2 593 PY2NSA F5NBU JN28 (x7)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee