Contest Calendar

Amateur radio contests — all 260 computed from sponsors’ own published rules

iCal feed/API

SARL · ZA

SARL HF CW Contest

The CW leg of SARL's August HF series: three hours on 20, 40 and 80 m, on the fourth Sunday.

Rules at mysarl.org.zaThe rules are the sponsor's. This page holds the dates and the facts.

When it runs

Fourth Sunday of August

  • 1400Z → 1700Z Sunday

Times are UTC, as the sponsor states them.

Next runnings

  1. → · 3h2027

    in 325 days

    Logs due

  2. → · 3h2028

    in 696 days

    Logs due

  3. → · 3h2029

    in 1060 days

    Logs due

  4. → · 3h2030

    in 1424 days

    Logs due

Operating

Modes
CW
Bands
80m40m20m

20, 40 and 80 m. SSB 14 125-14 350, 7 063-7 100 and 7 130-7 200, 3 603-3 650 and 3 700-3 800 kHz; CW 14 020-14 030, 7 000-7 040, 3 510-3 560 kHz. The segments 7 100-7 130 and 3 651-3 699 kHz are contest free.

Exchange
RS, RSQ or RST report and a consecutive serial number starting at 001.
Logs
ADIF, Cabrillo or MS Excel · due 5 days after the end
Who can enter
Anyone, anywhere.

The aim is 'to contact as many amateurs in Southern Africa as possible', but the scoring table's Area 9 is 'Stations in the rest of the world', so entry is not restricted to South Africa. This corrects an earlier assumption in this catalog that SARL contests were ZS-only, which was flagged 'Confirm' and turned out to be wrong.

Where this comes from

Checked against the sponsor
Yes. The rule on this page was read off SARL's own published rules. Link last confirmed 2026-08-19.
What the source says
2026 SARL Contest Manual Version 1.1 (2025-12-15), mysarl.org.za: '2.3. HF CW Contest on (4th Sunday) 23 August 2026 14:00 to 17:00 UTC'. CW frequencies: '3.2. CW: 14 020 to 14 030 kHz 7 000 to 7 040 kHz 3 510 to 3 560 kHz.' Exchange as for Phone. Checked against SARL's own published dates as well as its rules: SARL publishes SARL-Contests-2026-Calendar.ics on the same page, whose times carry TZID="South Africa Standard Time" (a fixed +0200, no DST -- its own X-CALSTART confirms 09:00 local as 07:00Z). That calendar is an independent second source for every date encoded here.
Recorded caveats
FOURTH Sunday, not last: in a five-Sunday August the two differ, and SARL writes '(4th Sunday)'. log_deadline_days is 5, which is the right DAY and not the right hour: SARL states 'by 21:59 UTC on Friday', and the contest ends at 17:00 UTC on the Sunday five days before, so the engine's derived log_due lands at 17:00 rather than 21:59. The day is exact in every year because both ends are tied to the same Sunday. The five hours are recorded here rather than papered over.

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=sarl-hf-cw

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.