PU8OMT — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving PU8OMT, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 10m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-08 and 2026-06-30.
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 2 FT8 messages attributed to PU8OMT as the transmitting token by decoded message structure across 2 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
- 2 messages
- Active dates
- 2 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 PU8OMT in decoded directed-looking exchanges:
Most frequent locator attributed to PU8OMT
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
- GI77
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 8,594 km (approx.)
- Last such locator decoded
- 2026-06-30 12:32 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 | PU8OMT S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 07-31 18:40 | 10m | - / -16 | DB8WK | +4 / - | 12 | ✓ Closing fragment |
| 07-30 18:37 | 10m | - / -11 | GB2CG | -4 / - | 20 | Partial capture |
| 07-26 13:54 | 10m | - / - | F4ETS | -18 / - | 2 | ✓ Closing fragment |
| 07-02 12:29 | 10m | - / - | IK4LZH | -6 / - | 2 | Partial capture |
| 06-30 12:23 | 10m | - / -19 | DO9PV | -11 / - | 3 | Partial capture |
| 06-30 12:08 | 10m | - / - | HB9CTU | +10 / - | 4 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 184945 -4 598 PU8OMT GB2CG -11 184045 +4 1387 PU8OMT DB8WK JO33 (x11) 184745 -19 2003 PU8OMT DK8EE JO41 184745 +7 1072 PU8OMT DB8WK 73 114615 -24 1854 PU8OMT DK8EE JO41
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee