PY2TIM — 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 PY2TIM, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 20m, across 2 UTC dates in the available aggregate history. Observed between 2026-08-28 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 3 FT8 messages attributed to PY2TIM as the transmitting token by decoded message structure across 2 UTC dates in the available aggregate history. The available sample contains attributed decodes on 20 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
- 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 PY2TIM in decoded directed-looking exchanges:
Most frequent locator attributed to PY2TIM
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
- GG68 · 3 decoded messages
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 10,415 km (approx.)
- Last such locator decoded
- 2026-08-29 20:58 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 | PY2TIM S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 10-15 01:52 | 40m | - / -11 | UN0GY | -9 / - | 3 | ✓ Closing fragment |
| 10-13 01:42 | 40m | - / -8 | VP2MAA | -7 / - | 3 | Partial capture |
| 08-29 20:56 | 20m | -19 / - | CT3CK | -15 / - | 2 | ✓ Closing observed |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 215530 -18 2183 PY2TIM PQ5TA RR73 014215 -9 634 PY2TIM VP2MAA -08 (x3) 015230 -8 2647 PY2TIM UN0GY -11 (x3)
UTC dB Audio Message 203530 -20 971 Z34K PY2TIM GG68 205645 -19 2177 CT3CK PY2TIM GG68 205730 -15 1460 PY2TIM CT3CK RR73 205845 -17 2177 TA3HEB PY2TIM GG68
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.
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