N4YKU — 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 N4YKU, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-10-29.
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 N4YKU 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
- 2 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 N4YKU 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 | N4YKU S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 10-29 05:50 | 80m | - / -2 | PI4DX | -2 / - | 2 | ✓ Closing fragment |
| 10-29 05:45 | 80m | - / -1 | PI4DX | -6 / - | 2 | ✓ Closing fragment |
| 10-29 05:42 | 80m | - / -25 | DK7ZT | -6 / - | 3 | Partial capture |
| 10-29 05:41 | 80m | -24 / - | W8BI | - / - | 2 | ✓ Closing fragment |
| 10-29 04:17 | 80m | - / - | UX5UO | +17 / - | 3 | Partial capture |
| 10-29 04:15 | 80m | - / -25 | DK7ZT | -4 / - | 5 | Partial capture |
| 10-29 04:14 | 80m | - / - | F5PBG | -8 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 035445 -12 1540 N4YKU IZ8DBJ JN70 (x2)
UTC dB Audio Message 041745 -2 1759 N4YKU DK7ZT -25 041815 +20 831 N4YKU UX5UO KO50 054130 -24 1560 W8BI N4YKU R+11 (x2) 054245 -5 1759 N4YKU DK7ZT -25 (x3) 054545 -6 964 N4YKU PI4DX -01 (x2) 054645 +4 602 N4YKU F4LZZ JN09 054645 -4 238 N4YKU DO1ID -18 055015 -5 964 N4YKU PI4DX -02 (x2) 055115 -19 355 N4YKU F4LZZ JN09 055145 -15 965 N4YKU F5MXH JN07
UTC dB Audio Message 050430 -24 1780 N4YKU C5R -05
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