Skip to content

IARU Band Plan (Region 1 · 2 · 3)

HAM-Tools ships the band plans for all three IARU regions — complete with sub-segment breakdown (CW · SSB · Digital · Beacons · Satellite · etc.). The data comes from the bundled bandplan.json in the app bundle.

The active region is derived from your callsign on first launch (Europe → R1, Americas → R2, Asia-Pacific → R3) and can be switched anytime at the top of the band plan window — the band edges and the awareness pill then use the selected region.

Three Ways to Access It

1. Sub-Tab in the Logbook

In the lower tab bar of every logbook type (DX, Contest and all outdoor programs) there's a "Band Plan" sub-tab. It shows the active band with all sub-segments as a ruler display. The CAT frequency is drawn in as a live marker — it shifts immediately when you QSY on the radio.

2. Dedicated Window (⌘⇧P) 🆕

New in 1.8.8

The shortcut ⌘⇧P or the menu Window → Band Plan Window opens the complete band plan in a standalone window — handy on a second monitor during logging or a contest.

In the window:

  • All 22 bands as horizontal rulers stacked under each other
  • Sub-segments color-coded by mode (CW blue, Digital violet, SSB orange, Beacons red, …)
  • The active CAT frequency as a red marker
  • Tooltip per sub-segment with mode + bandwidth + license class

3. Live Awareness Pill in All QSO Forms 🆕

New in 1.8.9

When you log, a pill in the status bar tells you immediately whether your current frequency + mode are IARU compliant.

PillMeaning
🟢 in bandfrequency in band, sub-segment fits the mode
🟠 wrong sub-segmentin band, but in the wrong area (e.g. SSB in the CW sub-segment)
🔴 outside amateur bandfrequency is not in a known band

Reacts live to CAT frequency changes. Active in all QSO forms (DX, Contest and all outdoor programs).

Implemented in BandplanChecker.swift — mode compatibility is kept tolerant: "all modes" sub-segments (e.g. wide areas from 50 MHz up) let everything through, so you don't get false positives in the 6 m band-plan wild west.

Band Overview

The app knows these bands:

Frequency rangeDesignation
135.7 – 137.8 kHz2200 m
472 – 479 kHz630 m
1810 – 1850 kHz160 m
3500 – 3800 kHz80 m
5351.5 – 5366.5 kHz60 m
7000 – 7200 kHz40 m
10100 – 10150 kHz30 m
14000 – 14350 kHz20 m
18068 – 18168 kHz17 m
21000 – 21450 kHz15 m
24890 – 24990 kHz12 m
28000 – 29700 kHz10 m
50 – 52 MHz6 m
70 – 70.5 MHz4 m
144 – 146 MHz2 m
430 – 440 MHz70 cm
1240 – 1300 MHz23 cm
2300 – 2450 MHz13 cm
3400 – 3410 MHz9 cm
5650 – 5850 MHz6 cm
10.0 – 10.5 GHz3 cm
24.000 – 24.050 GHz1.25 cm

Mode Compatibility (simplified)

ModeStandard sub-segment
CWCW area (typically the band start)
SSBphone area (LSB <10 MHz, USB ≥10 MHz)
FT8/FT4/JT65dedicated digital segment (e.g. 7074 kHz for FT8 on 40 m)
RTTY/PSK31digital segment (often right below SSB)
AMmostly the phone segment
FMonly 10 m and up (29.5 MHz+, 6 m+, 2 m+)

Band-plan-specific special areas (beacons e.g. 14.099–14.101 MHz, satellite sub-segments, EME windows) are split out into bandplan.json — mode conflicts are detected there, but handled tolerantly (orange "wrong sub-segment" instead of "outside band").

Switching region (new in 1.36)

At the top of the band plan window you choose between R1 · R2 · R3:

  • Region 1 — Europe, Africa, Middle East (basis: IARU R1 + BAKOM/NaFV Switzerland)
  • Region 2 — the Americas (basis: ARRL/IARU R2; e.g. 40 m up to 7300 kHz, 60 m as 5 channels)
  • Region 3 — Asia-Pacific (basis: WIA/VK; e.g. 160 m only 1800–1875 kHz)

Band edges, sub-segments and power limits differ per region. The suggestion on first launch comes from your callsign but can be changed freely (portable, travel, curiosity).

The official band plan remains binding

The R2/R3 region plans are a solid starting point based on the major national band plans (ARRL, WIA). Details of individual calling frequencies or country-specific rules may differ — the official band plan of your national authority is always authoritative. Feedback on discrepancies is welcome.

HAM-Tools © HB9HJI · Funkwelt