RA4HEF — 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 RA4HEF, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 80m, 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-22 and 2026-10-21.
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 4 FT8 messages attributed to RA4HEF 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 (75%) and 80 m (25%). The sample is too small to infer a recurring UTC-hour or received-S/N pattern.
Overview
Bands
Last attributed message: 2026-10-21 17:14 UTC
Observed FT8 message patterns
- Attributed sample
- 4 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 RA4HEF in decoded directed-looking exchanges:
Most frequent locator attributed to RA4HEF
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
- LO53
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 2,036 km (approx.)
- Last such locator decoded
- 2026-06-22 13: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 | RA4HEF S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 10-28 17:25 | 80m | - / -8 | UA9FMT | -12 / - | 2 | ✓ Closing fragment |
| 10-21 17:14 | 80m | -24 / - | RK4HS | -16 / +3 | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 183645 -1 1067 RA4HEF HF50HSP -15 171400 -24 1815 RK4HS RA4HEF R+03 171415 -16 1815 RA4HEF RK4HS RRR 172500 -12 1926 RA4HEF UA9FMT -08 (x2) 181945 -22 1649 RA4HEF R4DB +14 182115 -11 1105 RA4HEF UA3SCU -15
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