NP4JL — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving NP4JL, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 20m, across 3 UTC dates in the available aggregate history. Observed between 2026-06-13 and 2026-08-25.
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 3 FT8 messages attributed to NP4JL as the transmitting token by decoded message structure across 3 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
- 3 messages
- Active dates
- 3 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 NP4JL 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 | NP4JL S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-13 22:29 | 20m | - / -15 | VE3ARF | -7 / - | 2 | ✓ Closing fragment |
| 07-27 22:37 | 20m | - / -4 | KE4EB | -8 / - | 2 | ✓ Closing fragment |
| 07-07 21:43 | 20m | - / -22 | DL1RBR | -2 / - | 4 | ✓ Closing fragment |
| 06-29 22:11 | 20m | - / -15 | DL4QB | -14 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 020000 -16 1252 NP4JL W4DXM R-04
UTC dB Audio Message 221130 -14 1425 NP4JL DL4QB R-15 (x2) 214330 +0 745 NP4JL DL1RBR R-22 (x4) 223745 -9 1153 NP4JL KE4EB R-04 (x2) 223530 -24 1717 NP4JL EC5M 73 222945 -9 444 NP4JL VE3ARF R-15 (x2) 223115 -20 1495 KJ5PWR NP4JL +03 191115 -24 1496 N1KAB NP4JL RR73
UTC dB Audio Message 014830 -18 2200 NP4JL K4BQP/4 R-16
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