Registry

Contests

Every contest in the register, with the years it has run. Finding the one you want is the whole job of this page — for an entrant looking up next weekend, and for a program fetching the rules.

312

Contests

1,847

Published versions

Sponsors

2016–2026

Instances covered

not yet available

Contest	Sponsor	Recurrence	Modes	Status	Slug	Version
CQ World Wide DX Contest, SSB	CQ Magazine	last full weekend of October	SSB	published	cq-ww-ssb	@3
CQ World Wide DX Contest, CW	CQ Magazine	last full weekend of November	CW	published	cq-ww-cw	@3
CQ WPX Contest, SSB	CQ Magazine	last full weekend of March	SSB	published	cq-wpx-ssb	@2
ARRL International DX Contest, CW	ARRL	third full weekend of February	CW	published	arrl-dx-cw	@1
IARU HF World Championship	IARU	second full weekend of July	CW, SSB	published	iaru-hf	@2
Helvetia Contest	USKA	last full weekend of April	CW, SSB, RTTY	published	helvetia	@1
WAE DX Contest, CW	DARC	second full weekend of August	CW	superseded	wae-cw	@2
RSGB IOTA Contest	RSGB	last full weekend of July	CW, SSB	published	iota	@1
CQ WW RTTY DX Contest	CQ Magazine	last full weekend of September	RTTY	published	cq-ww-rtty	@2
All Asian DX Contest, CW	JARL	third full weekend of June	CW	draft	aa-dx-cw	@1

example Invented rows, not live data. The citable reference of a real definition is acd:<uuid>@<version> — the slug is only the human handle, and the uuid is what a consumer pins.

What a detail page shows

The most important page of the site. Written out in plain language and tables so a person can read it, with the machine-readable version alongside rather than instead.

→When it runs, both as the rule says it and as real dates in UTC for the year you pick
→Which bands and modes are allowed, as a plain list
→What the two stations exchange, with an example of each field
→The point rules, numbered, saying plainly that the first rule that fits decides
→What multiplies the total, and whether it counts once or once per band
→A worked example with real numbers, so you can check the rules were read correctly

That last one matters most. Anyone can write down rules that look right; a worked example that comes out to the correct score is the proof they were understood.

The other view — machine-readable

$ curl https://api.contestdatabase.org/v1/contests/cq-ww-ssb
{
  "reference":  "acd:9f2b6d41-7c33-4a8e-b5d0-1e8a7c4f2b90@3",
  "uuid":       "9f2b6d41-7c33-4a8e-b5d0-1e8a7c4f2b90",
  "slug":       "cq-ww-ssb",
  "name":       "CQ World Wide DX Contest, SSB",
  "sponsor":    "CQ Magazine",
  "status":     "published",
  "instances":  [2024, 2025, 2026],
  "schema":     "https://api.contestdatabase.org/v1/contest.schema.json"
}

Endpoint shape is a placeholder. URLs become part of the spec and cannot break afterwards, so they are deliberately still open.

Diff view

"What changed between @2 and @3?" is a question a standards body has to be able to answer — sponsors, developers and adjudicators all ask it. Field-wise comparison between any two versions.