SARTG WW RTTY Contest

Scandinavia's flagship RTTY contest: three eight-hour periods split across a weekend, so operators get enforced rest.

Rules at sartg.comThe rules are the sponsor's. This page holds the dates and the facts.

When it runs

Third full weekend of August

0000Z → 0800Z Saturdaysession 1
1600Z → 2400Z Saturdaysession 2
0800Z → 1600Z Sundaysession 3

Times are UTC, as the sponsor states them.

3 sessions run off the one anchor day; each is a separate running with its own log.

Next runnings

0000Z Sat 21 Aug → 0800Z Sat 21 Aug · 8h2027
in 323 days
1600Z Sat 21 Aug → 0000Z Sun 22 Aug · 8h2027
in 324 days
0800Z Sun 22 Aug → 1600Z Sun 22 Aug · 8h2027
in 324 days
0000Z Sat 19 Aug → 0800Z Sat 19 Aug · 8h2028
in 687 days
1600Z Sat 19 Aug → 0000Z Sun 20 Aug · 8h2028
in 688 days
0800Z Sun 20 Aug → 1600Z Sun 20 Aug · 8h2028
in 688 days

Operating

Modes: RTTY
Bands: 80m40m20m15m10m
Exchange: RST + QSO number starting with 001
Logs: no deadline or format recorded
Who can enter: Anyone, anywhere.
SARTG's rules pages list classes (including SWL) but state no entrant restriction. Worldwide is the strong reading, not a quote.

Where this comes from

Checked against the sponsor: Yes. The rule on this page was read off SARTG (Scandinavian Amateur Radio Teleprinter Group)'s own published rules. Link last confirmed 2026-08-12.
What the source says: sartg.com/contest/wwrules.htm: 'Third full weekend in August', '15 - 16 August 2026'. Contest Periods: 'Three (3) separate periods: 0000 - 0800 UTC Saturday / 1600 - 2400 UTC Saturday / 0800 - 1600 UTC Sunday'.
Recorded caveats: Three separate eight-hour periods with gaps between them, not one continuous 48-hour run -- encoded as three sessions off the Saturday anchor. SARTG's own '15 - 16 August 2026' is the independent check on the third-full-weekend rule.

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 Calendar Subscribe (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=sartg-ww-rtty

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.