SP6ATG — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving SP6ATG, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-09 and 2026-08-31.
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 SP6ATG as the transmitting token by decoded message structure across 2 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
- 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 SP6ATG in decoded directed-looking exchanges:
Most frequent locator attributed to SP6ATG
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
- JO81 · 2 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 379 km (approx.)
- Last such locator decoded
- 2026-06-09 23:44 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 | SP6ATG S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-31 10:57 | 20m | - / +1 | F5IXN | +2 / - | 3 | ✓ Closing fragment |
| 07-21 11:45 | 20m | - / +1 | GJ0KYZ | -12 / - | 2 | ✓ Closing fragment |
| 07-03 10:58 | 10m | - / - | EB3JT | -18 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 114545 -11 1216 SP6ATG GJ0KYZ +01 (x2) 114900 -20 1480 SP6ATG LZ1AAW RR73 151230 -14 251 SP6ATG EB5DFU -14 105615 -5 1038 RI1FJL SP6ATG R-05 105615 -9 1089 DL4OAJ/QRP <SP6ATG> RR73 105700 +4 1089 SP6ATG F5IXN JN23 (x3)
UTC dB Audio Message 105430 -20 1842 SP6ATG 7Q9BK +05 105845 -18 1479 SP6ATG EB3JT JN01 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee