VK4FH — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving VK4FH, decoded by SO8OO in southeastern Poland. 2 FT8 messages attributed to this token as transmitter, on 20m, across 1 UTC dates in the available aggregate history. Last observed 2026-08-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 2 FT8 messages attributed to VK4FH 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
- 2 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 VK4FH in decoded directed-looking exchanges:
Most frequent locator attributed to VK4FH
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
- QG64
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 15,057 km (approx.)
- Last such locator decoded
- 2026-08-29 04:55 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 | VK4FH S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-29 04:41 | 20m | -18 / -13 | RU3GF | -2 / - | 4 | ✓ Closing observed |
| 08-27 06:08 | 20m | - / -15 | DJ7JB | +8 / - | 9 | Partial capture |
| 08-27 06:07 | 20m | - / -14 | EA5JCI | -10 / - | 4 | Partial capture |
| 08-27 06:05 | 20m | - / -13 | F4LNM | +6 / - | 2 | Partial capture |
| 07-28 06:44 | 20m | - / - | IT9DVZ | -16 / - | 2 | ✓ Closing fragment |
| 07-28 06:42 | 20m | - / - | DG8GAE | -12 / - | 3 | Partial capture |
| 07-28 06:40 | 20m | - / - | EB3JT | -8 / - | 7 | ✓ Closing fragment |
| 07-28 06:38 | 20m | - / - | DG8GAE | -10 / - | 3 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 061815 -7 1240 VK4FH F4CQS -17
UTC dB Audio Message 060945 -10 2590 VK4FH EA5JCI R-14 061015 +9 851 VK4FH DJ7JB JO62 (x7) 061730 +4 724 VK4FH F4LZZ JN09 044145 +6 2728 VK4FH RU3GF -13 (x3) 044400 -18 947 RU3GF VK4FH 73 045530 -21 947 FR5CB VK4FH QG64 063130 -17 488 VK4FH F4LZZ JN09
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee