RSGB 3.5 MHz Autumn Series, SSB

When it runs

Dates set by the sponsor each year (no derivable rule)

• 1900Z → 2030Z

Times are UTC, as the sponsor states them.

The sponsor announces these dates a year at a time and there is no rule to derive, so this calendar holds only the years they have published: 2026.

Next runnings

1. 1900Z Thu 22 Oct → 2030Z Thu 22 Oct · 1h 30m2026

   in 21 days

   Logs due 2030Z Sun 25 Oct

2. 2000Z Wed 11 Nov → 2130Z Wed 11 Nov · 1h 30m2026

   in 41 days

   Logs due 2130Z Sat 14 Nov

Operating

Modes

SSB

Bands

80m

3600-3775 kHz.

Exchange

RS(T) plus a serial number starting at 1 and incrementing by 1.

Logs

due 3 days after the end

Who can enter

Anyone, anywhere.

RSGB lists 'non-UK stations as individuals' among the entrant categories alongside affiliated-society members and RSGB members, so entry is not restricted to the UK&CD as it is for AFS and Club Calls.

Where this comes from

Checked against the sponsor

Yes. The rule on this page was read off RSGB Contest Committee's own published rules. Link last confirmed 2026-08-23.

What the source says

rsgbcc.org/hf/rules/2026/rautumn.shtml, the RSGB Contest Committee's own rules for the 'RSGB 3.5MHz Autumn Series Contests'. Dates and modes as printed: 7 September SSB, 16 September CW, 24 September Data, 5 October CW, 14 October Data, 22 October SSB, 2 November Data, 11 November SSB, 26 November CW. Times: 'September and October: 1900-2030 UTC' and 'November: 2000-2130 UTC'. Frequencies: 'CW: 3510-3565 kHz (any speed); 3565-3570 kHz (15wpm max). SSB: 3600-3775 kHz. PSK63: 3580-3590 kHz. RTTY: 3590-3620 kHz.' Exchange: 'RS(T) plus Serial Number starting at 1 and incrementing by 1'. Entrants: members of RSGB Affiliated Societies, RSGB members as individuals, NON-UK STATIONS AS INDIVIDUALS, and members of the RSGB Contest Club. Logs: 'by 23:59:59 (UTC) on the third day following each contest'. Checked 2026-08-23.

Recorded caveats

THE CLOCK MOVES IN NOVEMBER AND THE RECORD SAYS SO PER DATE. September and October run 1900-2030 UTC; November runs 2000-2130. Every leg of this series sits on one side or the other of that change, so a single stored time would put two of the three runnings on the calendar an hour wrong. This is the first use of PER-DATE TIMES in a manual rule, a schema question NEEDS_A_HUMAN had been carrying since the REP FT4 series hit the same wall. The alternative was one record per clock time -- six records for a nine-leg series the sponsor treats as one -- or one record per leg, which is nine. Splitting by MODE is the split a reader actually wants, because the mode filter is what they reach for, and per-date times are what make that split possible without lying about an hour. MANUAL BECAUSE RSGB PUBLISHES DATES AND NO RULE for this series. The legs fall on Mondays, Wednesdays and Thursdays with no discernible ordinal, which is exactly the shape an ordinal must not be fitted to. NON-UK STATIONS MAY ENTER AS INDIVIDUALS -- RSGB states it outright, which is worth noting beside the AFS and Club Calls contests where entry really is UK&CD only.

Something wrong? How to report it — a link to the sponsor's own page is all it takes.

Take it with you

Add to Google CalendarSubscribe (iCal)This record as JSON

Add to Google Calendar puts the next running in as a single event. It is one event, not a subscription — come back for the one after it, or use the feed below.

Subscribe (iCal) carries this contest's runnings for the next twelve months as UTC instants and keeps them current. Apple Calendar, Outlook and Thunderbird take this address directly. Its identifiers are stable across deploys, so re-subscribing does not duplicate anything: https://contestclock.com/api/ics?id=rsgb-autumn-ssb

Google has no working one-click subscribe. Paste that address into Settings → Add calendar → From URL. Google then polls it on its own schedule, often 8–24 hours, and that cannot be forced — so use Add to Google Calendar above if you want the next running in your calendar now.