PY2CAB — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving PY2CAB, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 10m, across 3 UTC dates in the available aggregate history. Observed between 2026-06-06 and 2026-06-16.
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 3 FT8 messages attributed to PY2CAB as the transmitting token by decoded message structure across 3 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
- 3 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 PY2CAB in decoded directed-looking exchanges:
Most frequent locator attributed to PY2CAB
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
- GG56 · 3 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 10,716 km (approx.)
- Last such locator decoded
- 2026-06-16 18:17 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 | PY2CAB S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-23 19:19 | 10m | - / -19 | IU8ADS | -7 / - | 4 | ✓ Closing fragment |
| 07-18 19:10 | 10m | - / -21 | RM3DA | +7 / - | 3 | ✓ Closing fragment |
| 07-18 19:04 | 10m | - / - | UA3AVY | -8 / - | 2 | Partial capture |
| 07-17 19:16 | 10m | - / - | RW4M | -19 / - | 2 | Partial capture |
| 06-26 19:22 | 10m | - / - | RN4AQ | -12 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 192345 -10 1055 PY2CAB RN4AQ 73 164300 -21 1161 PY2CAB RW4M LO44 191315 -23 1350 PY2CAB G3TKT IO92 191615 -19 1346 PY2CAB RW4M LO44 (x2) 194945 -21 1752 PY2CAB RD3AW KO85 190445 -6 1475 PY2CAB UA3AVY KO95 (x2) 191045 +7 1173 PY2CAB RM3DA KO95 (x3) 191945 +0 1023 PY2CAB IU8ADS JN70 (x4)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee