4Z5PJ — FT8 activity observed at SO8OO

DXCC entity inferred from callsign: Israel Most frequent locator attributed to this token: KM71

Receiver-side FT8 activity involving 4Z5PJ, decoded by SO8OO in southeastern Poland. 7 FT8 messages attributed to this token as transmitter, on 40m, 20m, across 3 UTC dates in the available aggregate history. Observed between 2026-06-16 and 2026-08-29.

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 7 FT8 messages attributed to 4Z5PJ as the transmitting token by decoded message structure across 3 UTC dates in the available aggregate history. The largest monitored-band total was 40 m (71%), followed by 20 m (29%). In this small sample, the estimated median decoder S/N was -15 dB; no usual signal pattern is inferred.

Overview

7
Messages attributed
3
UTC dates decoded
3
Active 15-min windows
-15 dB
Estimated median S/N

Bands

First attributed message: 2026-06-16
Last attributed message: 2026-08-29 18:10 UTC

Observed FT8 message patterns

Attributed sample
7 messages
Active dates
3 UTC dates
Estimated median S/N
-15 dB
S/N percentile sample
Too small
Recurring-pattern threshold
Not met

SO8OO display ranges among successful decodes: weak (≤ -16 dB) 2, moderate (-15 to -9 dB) 5, strong (≥ -8 dB) 0.

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).

Most frequent locator attributed to 4Z5PJ

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
KM71 · 6 decoded messages
SO8OO receiver locator
KN09VW
Locator-centre separation
2,325 km (approx.)
Last such locator decoded
2026-08-29 18:10 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 UTCBand4Z5PJ S/NCounterpartCounterpart S/NMsgsCapture
08-30 08:44 20m - / - IU6KQP -6 / - 3 Partial capture
08-29 18:10 20m -14 / - MI7IHF -4 / - 2 Partial capture

Recent FT8 messages decoded at SO8OO

Frequency values are decoder audio offsets in hertz, not RF frequencies.

20m
UTC    dB Audio  Message
080015 -22 1843  MI0NWA 4Z5PJ KM71
181030 -14 1848  MI7IHF 4Z5PJ KM71
181145 -12 1563  4Z5PJ HB9EKJ JN47
181215  -4 1541  4Z5PJ MI7IHF R IO65
084430  -5 1850  4Z5PJ IU6KQP JN63 (x3)

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