Contest Calendar

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

iCal feed/API

URE · ES

Concurso Municipios Espanoles (CME)

URE's Spanish municipalities contest: two SSB sessions over the second full weekend of August, Spanish stations sending their municipality number.

Rules at concursos.ure.esThe rules are the sponsor's. This page holds the dates and the facts.

When it runs

Second full weekend of August

  • 1200Z → 2259Z Saturdaysession 1
  • 0500Z → 1159Z Sundaysession 2

Times are UTC, as the sponsor states them.

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

Next runnings

  1. → · 10h 59m2027

    in 317 days

    Logs due

  2. → · 6h 59m2027

    in 317 days

    Logs due

  3. → · 10h 59m2028

    in 681 days

    Logs due

  4. → · 6h 59m2028

    in 681 days

    Logs due

  5. → · 10h 59m2029

    in 1045 days

    Logs due

  6. → · 6h 59m2029

    in 1045 days

    Logs due

Operating

Modes
SSB
Bands
80m40m20m15m10m
Exchange
Spanish stations send RS(T) + the number of their municipality (EA4URE sends HQ); DX stations send RS(T) + a serial number beginning with 001.
Power categories
High PowerLow Power 100 WQRP 5 W
Logs
Cabrillo · due 15 days after the end · concursos.ure.es
Who can enter
Anyone, anywhere.

'Participants: Any licensed amateur station.'

Where this comes from

Checked against the sponsor
Yes. The rule on this page was read off URE's own published rules. Link last confirmed 2026-08-18.
What the source says
concursos.ure.es/en/cme/bases/: 'Sponsored by: Union de Radioaficionados Espanoles (URE).' 'Participants: Any licensed amateur station.' 'Dates: 2nd full weekend of August, from 12:00 UTC Saturday until 22:59 UTC, and from 05:00 UTC until 11:59 UTC Sunday (August 8th and 9th 2026).' 'Mode: SSB.' 'Bands: 10, 15, 20, 40 and 80 meters'. 'Exchange: Spanish stations: RS (T) and number of the municipality. EA4URE will pass the abbreviation HQ. DX stations: RS (T) and serial number beginning with 001.' 'Logs must be received by 24th August 2026 (15 days).' That is exactly the second session's end instant plus 15 days.
Recorded caveats
Two sessions with an overnight break, encoded in the sessions array; the top-level start/end repeat the first session, as elsewhere in this catalog. URE states one deadline for the contest as a whole and it is the second session's end plus 15 days exactly. The engine applies log_deadline_days to each session separately, so the first session's computed deadline falls a day before URE's printed one. Dropping the interval to quote a fixed date instead would lose the arithmetic URE actually states, so the interval is kept and the artefact recorded here.

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=ure-cme

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.