RW9UBP — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving RW9UBP, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-08-26 and 2026-08-31.
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 RW9UBP as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The available sample contains attributed decodes on 20 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 RW9UBP in decoded directed-looking exchanges:
Most frequent locator attributed to RW9UBP
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
- NO36
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 4,234 km (approx.)
- Last such locator decoded
- 2026-08-31 06:02 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 | RW9UBP S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-31 07:09 | 20m | - / -23 | R7OV | +4 / - | 6 | Partial capture |
| 08-30 07:25 | 20m | - / -18 | UB4CLL | -11 / - | 3 | Partial capture |
| 08-30 07:19 | 20m | - / -10 | R3RRC/1 | -7 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 024915 -2 1079 RW9UBP W5GRP FN65 025600 -21 1584 RX7O RW9UBP 73 071230 -8 1912 RW9UBP R4FDW -03 071930 -10 2732 RW9UBP R3RRC/1 -10 (x2) 072500 -11 1581 RW9UBP UB4CLL -18 (x3) 060230 -19 2063 R6ZB RW9UBP NO36 070900 +7 2032 RW9UBP R7OV KN87 (x6)
Decoder S/N history by band
Count-weighted daily averages across messages attributed to this profiled token and successfully decoded at SO8OO, limited to the rolling 90-day UTC chart window.
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee