JG3RWX — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving JG3RWX, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 40m, across 2 UTC dates in the available aggregate history. Observed between 2026-09-11 and 2026-09-13.
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 JG3RWX 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 (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
- 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 JG3RWX in decoded directed-looking exchanges:
Most frequent locator attributed to JG3RWX
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
- PM74 · 2 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 8,565 km (approx.)
- Last such locator decoded
- 2026-09-13 20:31 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 | JG3RWX S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-20 21:01 | 80m | - / -18 | OH2BV | +18 / - | 2 | Partial capture |
| 09-20 20:32 | 80m | - / - | LA9GX | +2 / - | 2 | Partial capture |
| 09-20 20:32 | 80m | - / - | RT6Z | +2 / - | 2 | Partial capture |
| 09-20 20:31 | 80m | - / -10 | UX1AA | +4 / - | 10 | ✓ Closing fragment |
| 09-20 20:30 | 80m | - / -14 | EA6Y | +4 / - | 4 | ✓ Closing fragment |
| 09-20 20:25 | 80m | - / -3 | OZ1ADL | +6 / - | 3 | Partial capture |
| 09-20 20:12 | 80m | - / - | IV3GHY | +10 / - | 2 | Partial capture |
| 09-20 20:12 | 80m | - / -3 | LY3KI | +10 / - | 3 | ✓ Closing fragment |
| 09-20 20:12 | 80m | - / - | UX1AA | -1 / - | 5 | Partial capture |
| 09-20 20:10 | 80m | - / -4 | OZ1ADL | -1 / - | 2 | ✓ Closing fragment |
| 09-20 20:08 | 80m | - / 0 | YL3CW | +2 / - | 3 | ✓ Closing fragment |
| 09-19 20:56 | 40m | - / - | F5NBU | +10 / - | 4 | Partial capture |
| 09-19 20:55 | 40m | - / -10 | CN8NS | -10 / - | 2 | ✓ Closing fragment |
| 09-19 20:48 | 80m | - / - | DF7EF | +17 / - | 8 | Partial capture |
| 09-19 20:48 | 80m | - / -18 | 4X1UF | -12 / - | 16 | Partial capture |
| 09-19 20:15 | 80m | - / -15 | OH5KNL | +14 / - | 2 | ✓ Closing fragment |
| 09-19 20:11 | 80m | - / - | UX1AA | +6 / - | 5 | Partial capture |
| 09-19 20:08 | 80m | - / -15 | PI4DX | +13 / - | 5 | Partial capture |
| 09-16 20:45 | 40m | - / - | HB9HOG | -3 / - | 2 | Partial capture |
| 09-16 20:38 | 80m | - / -15 | SV1DKR | -5 / - | 3 | Partial capture |
| 09-13 20:31 | 40m | -22 / -7 | EX7CQ | 0 / - | 3 | ✓ Closing observed |
| 09-13 20:24 | 80m | - / -15 | S59A | +24 / - | 2 | ✓ Closing fragment |
| 09-11 20:55 | 40m | - / - | F5PBG | +3 / - | 3 | Partial capture |
| 09-11 20:18 | 40m | - / - | DJ0MAB | +6 / - | 2 | Partial capture |
| 09-11 20:18 | 40m | - / - | PD1EN | -5 / - | 5 | Partial capture |
| 09-11 20:17 | 40m | - / -17 | EA8UP | +3 / - | 2 | ✓ Closing fragment |
| 08-30 16:41 | 80m | - / -14 | YO4NT | +6 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 203215 -4 1843 JG3RWX SV1DKR KM18 203215 +11 2342 JG3RWX EA6Y 73 203245 +11 2657 JG3RWX UX1AA R-10 203245 +7 1053 JG3RWX RT6Z KN98 203245 +5 872 JG3RWX LA9GX JO59 203315 +5 2657 JG3RWX UX1AA R-10 203315 -2 1054 JG3RWX RT6Z KN98 203315 -1 872 JG3RWX LA9GX JO59 203345 +9 2657 JG3RWX UX1AA R-10 (x5) 210100 +18 2593 JG3RWX OH2BV -18 (x2)
UTC dB Audio Message 203300 -2 1715 JG3RWX EX7CQ -07 (x2) 205115 -16 1922 JG3RWX UK8FF -08 205245 -6 2492 JG3RWX I0KMJ JN62 205745 -2 2531 JG3RWX EA1CQ -18 204545 -4 1230 JG3RWX HB9HOG JN36 (x2) 205400 +1 1214 JG3RWX M0XYF IO90 205500 -14 1886 JG3RWX CN8NS -10 (x2) 205600 +11 2056 JG3RWX F5NBU JN28 (x2) 205700 +3 1214 JG3RWX M0XYF IO90 205700 +11 2056 JG3RWX F5NBU JN28 (x2)
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