CT4SU — FT8 activity observed at SO8OO
Receiver-side FT8 activity involving CT4SU, decoded by SO8OO in southeastern Poland. 3 FT8 messages attributed to this token as transmitter, on 10m, across 1 UTC dates in the available aggregate history. Last observed 2026-06-10.
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 CT4SU as the transmitting token by decoded message structure across 1 UTC dates in the available aggregate history. The available sample contains attributed decodes on 10 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 CT4SU in decoded directed-looking exchanges:
Most frequent locator attributed to CT4SU
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
- IN51
- SO8OO receiver locator
- KN09VW
- Locator-centre separation
- 2,546 km (approx.)
- Last such locator decoded
- 2026-06-10 07:17 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 | CT4SU S/N | Counterpart | Counterpart S/N | Msgs | Capture |
|---|---|---|---|---|---|---|
| 08-23 14:22 | 10m | - / 0 | F4GUK | -4 / - | 2 | ✓ Closing fragment |
| 08-17 18:31 | 10m | - / - | R6YBU | -20 / - | 2 | Partial capture |
| 08-12 19:59 | 20m | - / - | F5IXN | -15 / - | 3 | Partial capture |
| 08-12 19:51 | 20m | - / -5 | IK4LZH | -4 / - | 3 | ✓ Closing fragment |
| 07-28 18:29 | 10m | - / -6 | PD0HSK | -11 / - | 4 | ✓ Closing fragment |
| 06-24 20:50 | 10m | - / -13 | IK2UCK | -9 / - | 3 | ✓ Closing fragment |
Recent FT8 messages decoded at SO8OO
Frequency values are decoder audio offsets in hertz, not RF frequencies.
UTC dB Audio Message 205045 -6 1622 CT4SU IK2UCK R-13 (x2) 182945 -10 1670 CT4SU PD0HSK JO22 (x4) 183545 -19 1759 CT4SU DN9DZ R-03 191715 -17 1597 CT4SU RW6ASO RR73 183115 -22 1574 CT4SU R6YBU LN04 (x2) 140515 -24 1583 CT4SU PA1HGM -16 (x2) 141945 -8 917 CT4SU F4GUK JN18 (x3)
UTC dB Audio Message 195115 -4 462 CT4SU IK4LZH JN54 (x3) 195915 -14 1671 CT4SU F5IXN JN23 (x3)
FT8DB and SO8OO WebSDR are a hobby project maintained solo. ☕ Buy me a coffee