AK3Y — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving AK3Y, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 20m, across 1 UTC dates in the available aggregate history. Last observed 2026-07-29.
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 3 FT8 messages attributed to AK3Y 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
- 3 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 AK3Y in decoded directed-looking exchanges:
Most frequent locator attributed to AK3Y
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
- FM19
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 7,310 km (approx.)
- Last such locator decoded
- 2026-07-29 22:59 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 | AK3Y S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-07 21:16 | 20m | - / -2 | IK4LZH | 0 / - | 4 | ✓ Closing fragment |
| 08-07 21:15 | 20m | - / - | DK2SP | -11 / - | 5 | Partial capture |
| 07-29 23:11 | 40m | - / 0 | SP6JIU | -2 / - | 2 | ✓ Closing fragment |
| 07-29 23:02 | 20m | -16 / - | UR4QWW | - / -16 | 2 | ✓ Closing fragment |
| 07-27 21:38 | 20m | - / - | DL1R | -10 / - | 4 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 213930 -9 2672 AK3Y DL1R JN58 (x2) 225915 -17 1212 CQ AK3Y FM19 a1 230245 -15 1212 UR4QWW AK3Y -16 (x2) 211115 +0 2529 AK3Y RQ6A RR73 211545 -8 1212 AK3Y DK2SP JN58 211615 +3 462 AK3Y IK4LZH JN54 211615 -4 1212 AK3Y DK2SP JN58 211645 -4 462 AK3Y IK4LZH JN54 211645 -14 1212 AK3Y DK2SP JN58 211715 +0 463 AK3Y IK4LZH R-02 211715 -12 1212 AK3Y DK2SP JN58 211745 -1 462 AK3Y IK4LZH 73 211815 -18 1213 AK3Y DK2SP JN58
UTC dB Audio Message 231130 -3 2663 AK3Y SP6JIU +00 (x2)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee