PY2YS — FT8 activity observed at SO8OO

DXCC entity inferred from callsign: Brazil Most frequent locator attributed to this token: GG66

Receiver-side FT8 activity involving PY2YS, decoded by SO8OO in southeastern Poland. 11 FT8 messages attributed to this token as transmitter, on 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-07 and 2026-07-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 11 FT8 messages attributed to PY2YS as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The largest monitored-band total was 20 m (100%). In this small sample, the estimated median decoder S/N was -19 dB; no usual signal pattern is inferred.

Overview

11
Messages attributed
2
UTC dates decoded
3
Active 15-min windows
-19 dB
Estimated median S/N

Bands

First attributed message: 2026-06-07
Last attributed message: 2026-07-26 21:20 UTC

Observed FT8 message patterns

Attributed sample
11 messages
Active dates
2 UTC dates
Estimated median S/N
-19 dB
S/N percentile sample
Too small
Recurring-pattern threshold
Not met

SO8OO display ranges among successful decodes: weak (≤ -16 dB) 10, moderate (-15 to -9 dB) 1, 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 PY2YS in decoded directed-looking exchanges:

Most frequent locator attributed to PY2YS

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
GG66 · 2 decoded messages
SO8OO receiver locator
KN09VW
Locator-centre separation
10,592 km (approx.)
Last such locator decoded
2026-07-26 21:14 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 UTCBandPY2YS S/NCounterpartCounterpart S/NMsgsCapture
09-12 00:39 40m - / - UR4QWW -19 / - 3 Partial capture
09-05 23:26 40m - / -8 DK7ZT -6 / - 3 ✓ Closing fragment
07-26 21:18 20m -21 / - IU7UTX - / - 4 ✓ Closing fragment
07-26 21:14 20m -19 / - HL2IDT - / -16 5 ✓ Closing fragment
07-12 19:07 20m - / -24 UA6LCF -13 / - 3 ✓ Closing fragment

Recent FT8 messages decoded at SO8OO

Frequency values are decoder audio offsets in hertz, not RF frequencies.

40m
UTC    dB Audio  Message
232630  -7 1906  PY2YS DK7ZT -08 (x3)
003945 -19 1577  PY2YS UR4QWW KN77 (x3)
20m
UTC    dB Audio  Message
190730 -13 1939  PY2YS UA6LCF LN07 (x3)
211415 -19 1714  HL2IDT PY2YS GG66 (x5)
211645 -23 1714  JH5HDA PY2YS -18
211815 -22 1713  IU7UTX PY2YS RR73 (x4)

FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee