OZ4AY — 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 OZ4AY, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-11-04.
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 OZ4AY 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
- 4 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 OZ4AY in decoded directed-looking exchanges:
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 | OZ4AY S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 11-04 22:27 | 80m | 0 / -16 | EA1IOK | -16 / -3 | 7 | ✓ Full exchange observed |
| 11-04 22:25 | 80m | +2 / -20 | M0BEW | -2 / -4 | 4 | ✓ Full exchange observed |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 222530 -2 402 OZ4AY M0BEW -20 (x2) 222615 +4 401 M0BEW OZ4AY R-04 (x2) 222700 -18 1368 OZ4AY EA1IOK IN62 (x3) 222815 +1 400 EA1IOK OZ4AY -03 222830 -14 1368 OZ4AY EA1IOK R-16 222845 +0 401 EA1IOK OZ4AY RRR 222900 -15 1368 OZ4AY EA1IOK 73
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