All Asian DX Contest, CW

JARL's CW leg of the All Asian DX Contest: 24 hours over the third weekend in June, exchanging signal report and the operator's age.

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

When it runs

Third Saturday of June

0000Z Saturday → 2400Z Sunday

Times are UTC, as the sponsor states them.

Next runnings

0000Z Sat 19 Jun → 0000Z Mon 21 Jun · 48h2027
in 260 days
0000Z Sat 17 Jun → 0000Z Mon 19 Jun · 48h2028
in 624 days
0000Z Sat 16 Jun → 0000Z Mon 18 Jun · 48h2029
in 988 days
0000Z Sat 15 Jun → 0000Z Mon 17 Jun · 48h2030
in 1352 days

Operating

Modes: CW
Bands: 160m80m40m20m15m10m
Exchange: RS(T) and the operator's age. An operator who does not want to send an age sends 01. Multi-operator stations send the average age of the operators at the start of the contest.
Power categories: High PowerLow Power 100 W
Logs: Cabrillo · contest.jarl.org
Who can enter: Anyone, anywhere.
Anyone may enter. Asian stations work everyone; non-Asian stations score only contacts with Asian stations -- JARL: 'The points of completed contacts with Asian stations ... are shown below.' Not encoded as two_sided because that would need every Asian DXCC entity enumerated on both engines.

Where this comes from

Checked against the sponsor: Yes. The rule on this page was read off JARL's own published rules. Link last confirmed 2026-08-17.
What the source says: jarl.org (67th All Asian DX Contest rule): 'CW: (June 20-21,2026) From 00:00 UTC on the third Saturday in June to 24:00 UTC on the following day'. Bands: 'Amateur bands 160m, 80m, 40m, 20m, 15m, 10m'. Power: 'Low Power: Total output power must not exceed 100 watts. High Power: There is no limitation on total output power within the maximum allowable power level established by the national licensing authority'. The third Saturday in June 2026 is June 20, which is the date JARL prints. LOG DEADLINE DELIBERATELY NOT ENCODED: JARL states 'Logs must arrive at JARL no later than 10 days after the event is over. CW...July 1, 2026'. July 1 is 10 days after the last contest DAY (June 21), not 10 days after the 24:00 UTC end instant this record stores, so log_deadline_days would have to be 9 to reproduce JARL's own date. Rather than print a number JARL never wrote, the rule is quoted here and the field is omitted. Logs also go to aacw@jarl.org.

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=jarl-aa-dx-cw

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.