NJ2DX — 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 NJ2DX, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 20m, across 1 UTC dates in the available aggregate history. Last observed 2026-06-17.
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 NJ2DX as the transmitting token by decoded message structure across 1 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
- 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 NJ2DX in decoded directed-looking exchanges:
Most frequent locator attributed to NJ2DX
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
- FM29
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 7,189 km (approx.)
- Last such locator decoded
- 2026-06-17 01:40 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 | NJ2DX S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 10-19 14:55 | 10m | - / -10 | TN8GD | -11 / - | 2 | ✓ Closing fragment |
| 10-15 02:10 | 40m | - / -10 | MI7XHT | -17 / - | 2 | Partial capture |
| 08-10 21:21 | 20m | - / -8 | OK2CNI | -8 / - | 2 | ✓ Closing fragment |
| 08-08 04:42 | 40m | - / -12 | PI4DX | -6 / - | 6 | Partial capture |
| 08-02 06:07 | 40m | - / -15 | F4DIA | -16 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 145530 -10 722 NJ2DX TN8GD -10 (x2)
UTC dB Audio Message 060700 -17 1246 NJ2DX F4DIA -15 (x2) 044215 -6 1017 NJ2DX PI4DX -12 (x6) 021015 -22 2072 NJ2DX MI7XHT IO64 (x2)
UTC dB Audio Message 201215 -6 2695 NJ2DX PE2AE JO33 201245 +8 1300 NJ2DX S57ESG JN76 212100 -7 2445 NJ2DX OK2CNI -08 (x2)
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