JS2NYJ — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving JS2NYJ, decoded by SO8OO in southeastern Poland. 1 FT8 messages attributed to this token as transmitter, on 20m, across 1 UTC dates in the available aggregate history. Last observed 2026-06-14.
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 1 FT8 messages attributed to JS2NYJ 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
- 1 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 JS2NYJ in decoded directed-looking exchanges:
Most frequent locator attributed to JS2NYJ
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
- PM84
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 8,675 km (approx.)
- Last such locator decoded
- 2026-06-14 20:56 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 | JS2NYJ S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-20 13:28 | 20m | - / - | RA3ZH | -2 / - | 2 | Partial capture |
| 07-23 14:11 | 20m | - / - | IU5HIU | -17 / - | 3 | Partial capture |
| 07-23 14:08 | 20m | - / -11 | IK4IDF | -1 / - | 2 | ✓ Closing fragment |
| 06-27 15:19 | 20m | - / -10 | DL6LAG | -10 / - | 2 | ✓ Closing fragment |
| 06-27 15:13 | 20m | - / - | ON5TTT | -15 / - | 2 | Partial capture |
| 06-23 15:11 | 20m | - / - | F5PPO | -7 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 151130 -2 2177 JS2NYJ F5PPO JO10 151300 -18 2264 JS2NYJ ON5TTT JO11 (x2) 151915 -2 1909 JS2NYJ DL6LAG -10 (x2) 152045 -4 2416 JS2NYJ ON7KR JO20 140230 -19 1875 JS2NYJ PD0DEX -16 140815 +2 2831 JS2NYJ IK4IDF -11 (x2) 141145 -15 1293 JS2NYJ IU5HIU JN53 (x3) 132800 -6 2267 JS2NYJ RA3ZH KO81 (x2) 130800 -14 2396 JS2NYJ M7HET IO91
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee