PE2EP — 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 PE2EP, decoded by SO8OO in southeastern Poland. 18 FT8 messages attributed to this token as transmitter, on 80m, across 1 UTC dates in the available aggregate history. Last observed 2026-09-27.
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 18 FT8 messages attributed to PE2EP as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The largest monitored-band total was 80 m (100%). In this small sample, the estimated median decoder S/N was -2 dB; no usual signal pattern is inferred.
Overview
Observed FT8 message patterns
- Attributed sample
- 18 messages
- Active dates
- 1 UTC dates
- Estimated median S/N
- -2 dB
- S/N percentile sample
- Too small
- Recurring-pattern threshold
- Not met
SO8OO display ranges among successful decodes: weak (≤ -16 dB) 0, moderate (-15 to -9 dB) 3, strong (≥ -8 dB) 15.
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 PE2EP in decoded directed-looking exchanges:
Most frequent locator attributed to PE2EP
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
- JO22 · 3 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 1,201 km (approx.)
- Last such locator decoded
- 2026-09-27 18:49 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 | PE2EP S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 09-27 18:50 | 80m | +1 / -17 | UA4FKT | +2 / 0 | 19 | ✓ Full exchange observed |
| 09-27 18:49 | 80m | -6 / -18 | DO5SMH | -16 / -2 | 5 | ✓ Full exchange observed |
| 09-27 18:47 | 80m | -12 / - | SP7OK | - / - | 2 | Partial capture |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 185200 -3 506 UA4FKT PE2EP +00 (x12) 185745 -7 497 PE2EP UA4FKT R-17 185800 -2 505 UA4FKT PE2EP RRR 185815 -8 505 PE2EP UA4FKT 73
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