M0CRX — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving M0CRX, decoded by SO8OO in southeastern Poland. 6 FT8 messages attributed to this token as transmitter, on 80m, 40m, across 4 UTC dates in the available aggregate history. Observed between 2026-07-09 and 2026-09-04.
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 6 FT8 messages attributed to M0CRX as the transmitting token by decoded message structure across 4 UTC dates in the available aggregate history. The largest monitored-band total was 40 m (67%), followed by 80 m (33%). In this small sample, the estimated median decoder S/N was -8 dB; no usual signal pattern is inferred.
Overview
Bands
Last attributed message: 2026-09-04 04:52 UTC
Observed FT8 message patterns
- Attributed sample
- 6 messages
- Active dates
- 4 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) 1, strong (≥ -8 dB) 4.
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 M0CRX in decoded directed-looking exchanges:
Most frequent locator attributed to M0CRX
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
- IO91 · 3 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,607 km (approx.)
- Last such locator decoded
- 2026-09-04 04:51 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 | M0CRX S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-04 04:51 | 40m | -1 / - | K0SSD | - / -16 | 3 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 045615 -3 585 M0CRX YR50NADIA -05 045830 -21 1733 OS4K M0CRX 73 045100 -3 3029 K0SSD M0CRX IO91 (x3)
UTC dB Audio Message 035645 -13 1032 J88IH M0CRX IO91 043000 -8 2685 CQ M0CRX IO91
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.
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee