YO8PCD — reception at SO8OO
Signals decoded by SO8OO in southeastern Poland. FT8 and CW have separate histories; all times are UTC.
FT8 activity
Receiver-side FT8 activity involving YO8PCD, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-11-06.
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 YO8PCD as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The available sample contains attributed decodes on 80 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
- 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 YO8PCD in decoded directed-looking exchanges:
Most frequent locator attributed to YO8PCD
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
- KN38 · 2 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 411 km (approx.)
- Last such locator decoded
- 2026-11-06 04:50 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 | YO8PCD S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 11-06 04:58 | 80m | - / - | G0BLB | -2 / - | 2 | Partial capture |
| 11-06 04:57 | 80m | - / - | EA1IOK | -10 / - | 3 | Partial capture |
| 11-06 04:55 | 80m | +11 / 0 | YO4GIY | -5 / - | 2 | ✓ Closing observed |
| 11-06 04:50 | 80m | +9 / 0 | YO4GIY | -8 / - | 3 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 045000 +10 1756 YO4GIY YO8PCD KN38 (x2) 045145 -8 1756 YO8PCD YO4GIY +00 (x2) 045730 +11 1756 YO4GIY YO8PCD 73 045745 -9 701 YO8PCD EA1IOK IN62 045815 -4 357 YO8PCD SP5JMA KO02 045815 -4 2144 YO8PCD G0BLB IO81 045815 -14 701 YO8PCD EA1IOK IN62 045815 +6 1752 YO8PCD 9A4ZM JN86 045845 +0 2144 YO8PCD G0BLB IO81 045845 -7 701 YO8PCD EA1IOK IN62
CW
No CW receptions recorded for this callsign in the last 30 days.
Explore CW reception at SO8OOFT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee