N4MNK — 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 N4MNK, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 40m, 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-07-30 and 2026-09-11.
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 N4MNK as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The available sample contains attributed decodes on 40 m (50%) and 20 m (50%). The sample is too small to infer a recurring UTC-hour or received-S/N pattern.
Overview
Bands
Last attributed message: 2026-09-11 02:20 UTC
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 N4MNK 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 | N4MNK S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-11 02:19 | 40m | -9 / +6 | KB1EFS | -11 / - | 2 | ✓ Closing observed |
| 09-11 02:17 | 40m | - / - | RO7N | -8 / - | 4 | Partial capture |
| 09-11 02:16 | 40m | - / -17 | 4X5MZ | +10 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 021615 +10 789 N4MNK 4X5MZ -17 (x2) 021715 -10 2429 N4MNK RO7N KN97 (x4) 021915 -11 466 N4MNK KB1EFS +06 022000 -9 465 KB1EFS N4MNK 73
UTC dB Audio Message 020745 -7 395 RA4ABH N4MNK -03
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.
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