VA3LX — reception at SO8OO
Signals decoded by SO8OO in southeastern Poland. FT8 and CW have separate histories; all times are UTC.
FT8 activity
Receiver-side FT8 activity involving VA3LX, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 80m, across 2 UTC dates in the available aggregate history. Observed between 2026-09-21 and 2026-10-03.
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 VA3LX as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The available sample contains attributed decodes on 80 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 VA3LX in decoded directed-looking exchanges:
Most frequent locator attributed to VA3LX
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
- FN14 · 2 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 6,917 km (approx.)
- Last such locator decoded
- 2026-09-21 23:30 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 | VA3LX S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 10-27 00:53 | 160m | - / - | LX1JX | +4 / - | 2 | Partial capture |
| 10-27 00:35 | 160m | - / - | LX1JX | +5 / - | 2 | Partial capture |
| 10-27 00:28 | 160m | - / -16 | F5UKW | +7 / - | 2 | ✓ Closing fragment |
| 10-27 00:19 | 160m | - / -17 | HA6ZB | -5 / - | 4 | Partial capture |
| 10-27 00:17 | 160m | - / -14 | SV9CVY | +6 / - | 4 | ✓ Closing fragment |
| 10-27 00:10 | 160m | - / -20 | 9A5E | -7 / - | 2 | ✓ Closing fragment |
| 10-26 00:38 | 80m | - / - | PA3KUS | -5 / - | 3 | Partial capture |
| 10-26 00:23 | 160m | - / -19 | E77EA | -5 / - | 2 | ✓ Closing fragment |
| 10-26 00:23 | 160m | - / - | F5UKW | -19 / - | 6 | Partial capture |
| 10-03 22:41 | 80m | -24 / - | TF3VS | -10 / - | 3 | ✓ Closing observed |
| 09-25 23:56 | 40m | - / -14 | UR1CCT | -10 / - | 3 | ✓ Closing fragment |
| 09-25 23:01 | 80m | - / -22 | IZ5NRF | +11 / - | 3 | ✓ Closing fragment |
| 09-25 23:00 | 80m | - / -14 | ON6AA | +10 / - | 3 | ✓ Closing fragment |
| 09-21 23:55 | 80m | - / - | DH3MFW | +1 / - | 3 | Partial capture |
| 09-21 23:29 | 80m | -24 / -20 | RI1FJZ | -24 / -12 | 4 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 001815 +7 2593 VA3LX SV9CVY R-14 (x2) 001945 -6 2479 VA3LX HA6ZB -17 (x2) 002045 +7 2593 VA3LX SV9CVY 73 002045 -4 2478 VA3LX HA6ZB -17 (x2) 002345 -1 2177 VA3LX CT1FPQ IN50 (x2) 002815 +7 2308 VA3LX F5UKW -16 (x2) 003515 +3 2972 VA3LX LX1JX JO30 (x4)
UTC dB Audio Message 235530 +5 796 VA3LX DH3MFW JN58 (x3) 230015 +13 1075 VA3LX ON6AA JO11 (x3) 230145 +8 1899 VA3LX IZ5NRF JN53 (x3) 224145 -11 1845 VA3LX TF3VS HP94 224230 -24 2025 TF3VS VA3LX RR73 224245 -9 1845 VA3LX TF3VS 73 003830 -8 524 VA3LX PA3KUS JO21 (x3)
UTC dB Audio Message 235615 -11 681 VA3LX UR1CCT KN69 (x3)
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.
CW
No CW receptions recorded for this callsign in the last 30 days.
Explore CW reception at SO8OOFT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee