WB4GLJ — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving WB4GLJ, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 20m, across 3 UTC dates in the available aggregate history. Observed between 2026-06-09 and 2026-06-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 4 FT8 messages attributed to WB4GLJ 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
- 4 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 WB4GLJ in decoded directed-looking exchanges:
Most frequent locator attributed to WB4GLJ
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
- EM72 · 3 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 8,369 km (approx.)
- Last such locator decoded
- 2026-06-13 01:18 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 | WB4GLJ S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-07 23:28 | 40m | - / -12 | SQ100PKP | -7 / - | 3 | Partial capture |
| 09-03 07:58 | 40m | - / - | IK1JUS | -7 / - | 2 | Partial capture |
| 09-03 07:53 | 40m | - / - | IK1JUS | -19 / - | 3 | Partial capture |
| 09-01 04:11 | 40m | - / -15 | IT9VCE | -2 / - | 4 | ✓ Closing fragment |
| 08-30 03:19 | 40m | - / - | EA5HM | -6 / - | 5 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 040315 +2 684 WB4GLJ IZ0MYH JN63 041145 -4 756 WB4GLJ IT9VCE -15 (x4) 074945 -10 2790 WB4GLJ GU0SUP -22 075330 -18 1969 WB4GLJ IK1JUS JN35 (x5) 234930 -13 757 WB4GLJ OK1WCF 73 232800 -10 1434 WB4GLJ SQ100PKP -12 (x3)
UTC dB Audio Message 005830 +2 2729 WB4GLJ 4Z5PG -21 063415 -8 2597 WB4GLJ EA3DG R-24
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee