PD2HCM — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving PD2HCM, decoded by SO8OO in southeastern Poland. 1 FT8 messages attributed to this token as transmitter, on 40m, across 1 UTC dates in the available aggregate history. Last observed 2026-09-14.
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 PD2HCM as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The available sample contains attributed decodes on 40 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 PD2HCM in decoded directed-looking exchanges:
Most frequent locator attributed to PD2HCM
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
- JO21
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,192 km (approx.)
- Last such locator decoded
- 2026-09-14 17:45 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 | PD2HCM S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-14 17:45 | 40m | -9 / -15 | I0XNH | +5 / - | 5 | Partial capture |
| 09-14 17:41 | 40m | - / - | DL8TV | +8 / - | 2 | Partial capture |
| 09-14 17:39 | 40m | - / -15 | DB1IUA | -4 / - | 2 | Partial capture |
| 09-14 17:02 | 40m | - / -20 | ON4CJU | +2 / - | 3 | ✓ Closing fragment |
| 09-13 17:05 | 40m | - / -5 | ON6SAT | -2 / - | 2 | ✓ Closing fragment |
| 07-08 07:59 | 20m | - / - | OE3HPT | -15 / - | 8 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 170530 -2 2636 PD2HCM ON6SAT -05 (x2) 165330 +2 2277 PD2HCM SN40KZE +05 170215 +3 2824 PD2HCM ON4CJU -20 (x3) 173930 -3 1837 PD2HCM DB1IUA -15 (x2) 174130 +8 2185 PD2HCM DL8TV JN49 (x2) 174515 -9 2683 I0XNH PD2HCM JO21 174530 +2 2681 PD2HCM I0XNH -15 (x4)
UTC dB Audio Message 075915 -24 1673 PD2HCM OE3HPT JN77 (x8)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee