SM3YRD — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving SM3YRD, decoded by SO8OO in southeastern Poland. 1 FT8 messages attributed to this token as transmitter, on 10m, across 1 UTC dates in the available aggregate history. Last observed 2026-08-16.
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 1 FT8 messages attributed to SM3YRD as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The available sample contains attributed decodes on 10 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
- 1 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 SM3YRD in decoded directed-looking exchanges:
Most frequent locator attributed to SM3YRD
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
- JP93
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,517 km (approx.)
- Last such locator decoded
- 2026-08-16 19:40 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 | SM3YRD S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-30 11:19 | 10m | - / -8 | 7Z1MM | -6 / - | 2 | Partial capture |
| 07-16 08:11 | 10m | - / - | <...> | -6 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 081100 -5 2521 SM3YRD <...> RR73 (x2) 213130 -15 892 SM3YRD XQ3MCC FF46 172700 -13 1029 SM3YRD R8DX RR73 194045 -22 1485 LW7GPE SM3YRD JP93 105145 +2 686 SM3YRD IU2VBP JN45 111930 -3 2866 SM3YRD 7Z1MM -08 (x2) 111600 -13 2538 SM3YRD V51WH RR73 091900 -14 2161 SM3YRD <...> -05 (x2) 105500 -24 1768 SM3YRD RR73; IK6ATS <...> -18
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee