VE3DZN — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving VE3DZN, decoded by SO8OO in southeastern Poland. 11 FT8 messages attributed to this token as transmitter, on 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-13 and 2026-08-30.
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 11 FT8 messages attributed to VE3DZN as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The largest monitored-band total was 20 m (100%). In this small sample, the estimated median decoder S/N was -8 dB; no usual signal pattern is inferred.
Overview
Observed FT8 message patterns
- Attributed sample
- 11 messages
- Active dates
- 2 UTC dates
- Estimated median S/N
- -8 dB
- S/N percentile sample
- Too small
- Recurring-pattern threshold
- Not met
SO8OO display ranges among successful decodes: weak (≤ -16 dB) 1, moderate (-15 to -9 dB) 3, strong (≥ -8 dB) 7.
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 VE3DZN in decoded directed-looking exchanges:
Most frequent locator attributed to VE3DZN
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
- IM99 · 6 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 2,129 km (approx.)
- Last such locator decoded
- 2026-08-30 18:29 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 | VE3DZN S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-30 18:42 | 20m | - / - | M8KUG | -6 / - | 3 | Partial capture |
| 08-30 17:52 | 20m | -10 / - | OD5ZZ | - / - | 2 | ✓ Closing fragment |
| 08-30 17:50 | 20m | -1 / -6 | ZA/IK3BNO | -14 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 175000 -14 581 VE3DZN ZA/IK3BNO -06 175015 -1 580 ZA/IK3BNO VE3DZN R+11 175200 -11 1036 OD5ZZ VE3DZN IM99 (x2) 180730 -8 717 M9DNC VE3DZN R-17 181215 -18 1882 VE3DZN SV9COL -13 182915 -16 1214 EX7DY VE3DZN IM99 184030 -17 375 VE3DZN RW3FY +00 184200 -3 2544 VE3DZN M8KUG IO81 (x3)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee