DB5JS — 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 DB5JS, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 40m, across 1 UTC dates in the available aggregate history. Last observed 2026-09-22.
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 3 FT8 messages attributed to DB5JS as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The available sample contains attributed decodes on 40 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
- 3 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 DB5JS in decoded directed-looking exchanges:
Most frequent locator attributed to DB5JS
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
- JN49
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 920 km (approx.)
- Last such locator decoded
- 2026-09-22 15:18 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 | DB5JS S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-22 15:32 | 40m | - / - | IV3VFP | -10 / - | 3 | Partial capture |
| 09-22 15:30 | 40m | - / -6 | IN3ADG | +2 / - | 2 | ✓ Closing fragment |
| 09-22 15:26 | 40m | -9 / +2 | ON1DGN | -11 / - | 2 | ✓ Closing observed |
| 09-22 15:24 | 40m | -5 / -16 | DL1AG | -17 / - | 3 | ✓ Closing observed |
| 09-22 15:19 | 40m | - / -21 | YO9PH | 0 / - | 2 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 151930 +2 2184 DB5JS YO9PH -21 151930 -16 1003 DB5JS F1IQH JN27 152000 -1 2185 DB5JS YO9PH RR73 152430 -18 1003 DB5JS DL1AG JN48 (x2) 152515 -5 1002 DL1AG DB5JS RR73 152630 -11 687 DB5JS ON1DGN +02 152715 -9 1002 ON1DGN DB5JS 73 152800 -13 1002 DB5JS F4PCM JN23 152830 -10 992 DB5JS DK6MR JO30 153000 -2 1277 DB5JS IN3ADG -06 (x2) 153200 -12 1537 DB5JS IV3VFP JN66 (x3)
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