ARRL 10 GHz and Up Contest, Round 2

Rules at arrl.orgThe rules are the sponsor's. This page holds the dates and the facts.

When it runs

Third full weekend of September

0900Z Saturday → 0759Z Monday

Times are UTC, as the sponsor states them.

Next runnings

0900Z Sat 18 Sep → 0759Z Mon 20 Sep · 46h 59m2027
in 351 days
Logs due 0759Z Wed 20 Oct
0900Z Sat 16 Sep → 0759Z Mon 18 Sep · 46h 59m2028
in 715 days
Logs due 0759Z Wed 18 Oct
0900Z Sat 15 Sep → 0759Z Mon 17 Sep · 46h 59m2029
in 1079 days
Logs due 0759Z Wed 17 Oct
0900Z Sat 21 Sep → 0759Z Mon 23 Sep · 46h 59m2030
in 1450 days
Logs due 0759Z Wed 23 Oct

Operating

Modes: Mixed
Bands: 3cm
10 GHz through light
Exchange: not recorded yet
Logs: due 30 days after the end
Who can enter: Anyone, anywhere.

Where this comes from

Checked against the sponsor: Yes. The rule on this page was read off ARRL's own published rules. Link last confirmed 2026-08-12.
What the source says: arrl.org/10-ghz-up: 'Third full weekend of August and September'; 'Each weekend begins 0900 UTC Saturday and runs through 0759 UTC Monday. Participation is limited to 42 hours of operating time in each of the two contest weekends.' ARRL adds: 'NOTE: This is a change from the previous start and end times in local time. Participants are reminded to log all contacts in UTC time.' Cross-checked against ARRL's published 2026 dates, August 15-17 and September 19-21.
Recorded caveats: CORRECTION: this was stored as a local-time contest running 0600 local Saturday to 2359 local Sunday. ARRL has since moved it to fixed UTC and says so explicitly in the rules. It is now a plain UTC record -- 0900Z Saturday to 0759Z Monday -- and carries no timezone or local_rolling flag. Operating time is capped at 42 hours inside that 47-hour window. Also resolves the suspected typo flagged earlier: ARRL's rule reads 'Third full weekend of August AND SEPTEMBER', so a single rule covers both rounds and the September anchor was right all along.

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=arrl-10ghz-leg2

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.