M6XFS — 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 M6XFS, decoded by SO8OO in southeastern Poland. 1 FT8 messages attributed to this token as transmitter, on 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-08-10.
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 M6XFS as the transmitting token by decoded message structure across 1 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
- 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 M6XFS in decoded directed-looking exchanges:
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 | M6XFS S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-10 19:05 | 40m | - / -7 | DK7ZT | -4 / - | 3 | Partial capture |
| 08-10 01:58 | 80m | -24 / -20 | DD0AM | -2 / -16 | 5 | ✓ Full exchange observed |
| 08-09 19:54 | 40m | - / -20 | PD0IFI | -8 / - | 3 | ✓ Closing fragment |
| 08-09 19:48 | 40m | - / -16 | 9A7BB | -12 / - | 3 | Partial capture |
| 08-09 19:42 | 40m | - / - | PD0IFI | -2 / - | 4 | Partial capture |
| 08-09 19:36 | 40m | - / -15 | DL3JHK | -14 / - | 3 | ✓ Closing fragment |
| 07-26 00:31 | 40m | - / -16 | PE1NPS | -15 / - | 2 | ✓ Closing fragment |
| 07-25 22:47 | 40m | - / -21 | DK4CH | -18 / - | 3 | ✓ Closing fragment |
| 07-25 22:43 | 40m | - / -10 | SP1NL | -3 / - | 2 | ✓ Closing fragment |
| 07-25 22:34 | 40m | - / -16 | R2BIU | -16 / - | 2 | ✓ Closing fragment |
| 07-25 22:30 | 40m | - / -2 | M0MLS | -18 / - | 2 | ✓ Closing fragment |
| 07-25 21:44 | 40m | - / -12 | SM7JKW | -11 / - | 5 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 194300 +0 422 M6XFS PD0IFI JO32 (x3) 194800 -13 2169 M6XFS 9A7BB R-16 (x3) 195430 -7 464 M6XFS PD0IFI JO32 (x3) 000830 -20 1346 M6XFS F4ACR -15 190530 -3 1906 M6XFS DK7ZT -07 190600 -1 1456 M6XFS F5PBG R-02 190600 -3 1906 M6XFS DK7ZT -07 (x2) 222500 -20 2006 M6XFS SP6FME JO90
UTC dB Audio Message 190000 -13 2542 M6XFS G4YKQ -14 015800 -1 682 M6XFS DD0AM -20 (x3) 015915 -24 1228 DD0AM M6XFS R-16 015930 -9 682 M6XFS DD0AM RR73
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