2M0BHR — 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 2M0BHR, decoded by SO8OO in southeastern Poland. 4 FT8 messages attributed to this token as transmitter, on 40m, 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-06-09 and 2026-06-13.
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 4 FT8 messages attributed to 2M0BHR as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The available sample contains attributed decodes on 40 m (50%) and 20 m (50%). The sample is too small to infer a recurring UTC-hour or received-S/N pattern.
Overview
Bands
Last attributed message: 2026-06-13 20:59 UTC
Observed FT8 message patterns
- Attributed sample
- 4 messages
- Active dates
- 2 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 2M0BHR in decoded directed-looking exchanges:
Most frequent locator attributed to 2M0BHR
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
- IO75 · 4 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,894 km (approx.)
- Last such locator decoded
- 2026-06-13 20:59 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 | 2M0BHR S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 11-07 14:29 | 40m | - / -7 | MX0HFC | -19 / - | 5 | Partial capture |
| 10-22 17:54 | 40m | - / -16 | ON6WDL | +16 / - | 2 | ✓ Closing fragment |
| 10-19 11:34 | 40m | - / -10 | DK7ZT | -9 / - | 2 | Partial capture |
| 10-13 17:37 | 40m | - / - | DJ0MAB | +2 / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 183015 -3 1557 2M0BHR TM14LEO -06 111515 -22 1895 2M0BHR PD1AC R-13 111715 -9 1291 2M0BHR DJ0BS JO52 173530 -7 1915 2M0BHR ON7AN -07 173700 +3 1915 2M0BHR DJ0MAB JN49 (x2) 113400 -9 2488 2M0BHR DK7ZT -10 (x2) 175445 +18 2868 2M0BHR ON6WDL -16 (x2) 142930 -20 1656 2M0BHR MX0HFC -07 (x5)
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