Contest Calendar

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

iCal feed/API

IARU Region 1 VHF+ Committee · INTL

IARU Region 1 UHF/Microwaves Contest

Region 1's UHF and microwave weekend: 24 hours on the first weekend of October, 435 MHz up to the millimetre bands.

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

When it runs

First Saturday of October

  • 1400Z Saturday → 1400Z Sunday

Times are UTC, as the sponsor states them.

Next runnings

  1. → · 24h2027

    in 350 days
  2. → · 24h2028

    in 721 days
  3. → · 24h2029

    in 1085 days
  4. → · 24h2030

    in 1449 days

Operating

Modes
CWSSBFM
Bands
70cm23cm13cm3cm

Sponsor names 435 MHz, 1.3, 2.4, 3.4, 5.7, 10 GHz and a millimetre group (24, 47, 76, 122, 134, 245 GHz). Only 70cm, 23cm, 13cm and 3cm are recorded as tokens; 3.4 GHz, 5.7 GHz and the millimetre bands have no token here.

Exchange
RS(T) + serial number from 001 per band + 6-character locator (e.g. 59003 JO20DB)
Logs
EDI
Who can enter
Anyone, anywhere.

Not encoded as an entity list: the sponsor limits entry to Region 1 ('All licensed radio amateurs in Region 1 may participate in the contest'; special high-power licences enter as check logs only), and enumerating every Region 1 entity is not done here. Stations elsewhere cannot enter but may be worked.

Where this comes from

Checked against the sponsor
Yes. The rule on this page was read off IARU Region 1 VHF+ Committee's own published rules. Link last confirmed 2026-10-15.
What the source says
VHF Handbook 10.03 (https://www.iaru-r1.org/wp-content/uploads/2026/02/VHF_Handbook_V10_03_final.pdf), section 'RULES IARU R1 50/70 MHZ, 145 MHZ AND UHF/uW CONTESTS': 'IARU Region 1 UHF/Microwaves contest will begin on the first Saturday of October'; 'Each contest will commence at 14:00 UTC on the Saturday and end at 14:00 UTC on the Sunday.' Sponsor's hub calendar: 2026 Oct 3-4. Categories: SO, MO (SO-LP, MO-LP and 6H on 435 MHz). Read 2026-10-15.
Recorded caveats
Log deadline is not a fixed offset (EDI 'no later than the first Wednesday following the contest weekend at 23:59:59 UTC'), so log_deadline_days is not encoded.

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=iaru-r1-uhf-uw

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.