Concurso Nacional CW (CNCW)

When it runs

Third full weekend of July

• 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. 1200Z Sat 17 Jul → 2259Z Sat 17 Jul · 10h 59m2027

   in 289 days

   Logs due 2259Z Sun 1 Aug

2. 0500Z Sun 18 Jul → 1159Z Sun 18 Jul · 6h 59m2027

   in 289 days

   Logs due 1159Z Mon 2 Aug

3. 1200Z Sat 15 Jul → 2259Z Sat 15 Jul · 10h 59m2028

   in 653 days

   Logs due 2259Z Sun 30 Jul

4. 0500Z Sun 16 Jul → 1159Z Sun 16 Jul · 6h 59m2028

   in 653 days

   Logs due 1159Z Mon 31 Jul

5. 1200Z Sat 21 Jul → 2259Z Sat 21 Jul · 10h 59m2029

   in 1024 days

   Logs due 2259Z Sun 5 Aug

6. 0500Z Sun 22 Jul → 1159Z Sun 22 Jul · 6h 59m2029

   in 1024 days

   Logs due 1159Z Mon 6 Aug

Operating

Modes

CW

Bands

80m40m20m15m10m

Exchange

RST + the provincial abbreviation. EA4URE sends RST and HQ; URE members operating from outside Spain send RST and SU.

Power categories

High Power 1000 WLow Power 100 WQRP 5 W

Logs

Cabrillo · due 15 days after the end · concursos.ure.es↗

Who can enter

Entry limited to EA, EA6, EA8, EA9. K stations may be worked but cannot submit an entry.

'Any EA and CEPT licensed station transmitting from EA (all districts, example EA1/W1XXX) and URE members, EA or foreigners, that are outside of Spain.' The second clause lets URE members enter from anywhere; the entity list records the transmitting-from-Spain requirement that applies to everyone else.

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/cncw/bases/: 'Sponsored by: Union de Radioaficionados Espanoles (URE).' 'Participants: Any EA and CEPT licensed station transmitting from EA (all districts, example EA1/W1XXX) and URE members, EA or foreigners, that are outside of Spain.' 'Dates: 3rd full weekend of July (July 18th and 19th, 2026), from 1200 UTC Saturday till 2259 UTC Saturday and from 0500UTC till 1159UTC Sunday).' 'Bands: 10, 15, 20, 40 and 80 meters'. 'High power ( Max. 1000 watts), Low power ( max. 100 watts ) and QRP (max. 5 watts).' 'Exchange: RST plus the provincial abbreviation. EA4URE will send RST and “HQ”, EA or foreigners, outside of Spain, will send RST and SU'. 'Logs must be received by 3 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-cncw

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.