Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Which awards are worth chasing first? DXCC, WAS, WAZ, IOTA, WPX, POTA and SOTA compared, plus LoTW and QSL pitfalls

ci_cover.jpg

Lots of operators end up chasing several award programs at once without ever deciding which ones deserve the effort. The programs reward different things, and the confirmation rules differ. A contact that counts nicely for one may be worth nothing for another. I'd like to compare notes on how people sort this out.

Here is a rough map of what each one rewards. Always check the sponsor's current rules, because details change.

DXCC (ARRL) is about entities, not countries in the political sense. The basic award starts at 100 confirmed entities, and there are mode-specific and band-specific endorsements. The Honor Roll is based on how close you are to the number of current entities, and deleted entities don't help there. The Challenge counts band-entities across the HF bands and 6 m, with a high threshold for the first level. Check the ARRL rules for exactly which bands count.

WAS needs all 50 states. It's the easiest of the big awards to start with, especially for stations outside North America who want a goal that mostly depends on band conditions and scheduling rather than rare expeditions. WAC needs the six continents and is usually the first certificate people collect. WAZ (CQ) needs all 40 CQ zones. Some zones, particularly in parts of Asia and the Pacific, can be much harder than a simple map suggests.

CQ WPX counts prefixes, so ordinary QSOs with everyday stations add up quickly, and you don't need a rare entity to make progress. IOTA (RSGB) counts island groups with reference numbers such as EU-005, and many groups are not separate DXCC entities. CQ DX Marathon is a yearly competition in which entities and zones are counted for that year only, so every January the scoreboard resets.

POTA and SOTA are a different kind of chase. They reward activating or hunting reference locations (parks or summits), and the logging and award systems are separate from DXCC-style programs. Many operators work both sides of them for fun, but the records live in different places.

Questions for the thread:

  • How do you decide whether to chase a band-specific, mode-specific or mixed goal first?
  • How do you keep your LoTW account, paper QSLs and a local log from drifting apart?
  • Do deleted entities still motivate anyone, or do you just focus on the current list?
  • What is the best way to catch busted callsigns, wrong grid squares or wrong CQ zones before they cause award headaches?
  • Replies 2
  • Views 11
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

My suggestion for someone starting out is to pick one primary award and let the others come along as side effects. WAS and WAC fall out of regular operating, and a WPX tally grows without much planning. DXCC takes longer, so give it a clean base: one master log, with the confirmation status of each QSO recorded in its own field.

On LoTW, a match depends on both stations uploading signed logs with consistent data. That means call, band, mode and time need to agree within the matching tolerance. The usual reasons for a missing confirmation are a wrong mode (for example, logging FT8 as plain DATA in one place and something else in another), a portable or alternate callsign that was never added to your certificate setup, or a QSO date that fell on the wrong side of UTC midnight. If a QSO should be there and isn't, check those before assuming the other station never uploaded.

For entity credit, remember that DXCC is based on the entity list in effect and on the callsign and date of the contact. A QSO with a station operating from a location that was a different entity at that time counts for that entity, not today's. Deleted entities still sit in your overall total but not in the Honor Roll calculation, which is worth knowing before you spend time chasing old paper QSLs.

  • Moderators

I'd also separate the programs by who does the verification, because it changes your workflow. DXCC applications can use LoTW credits, and paper cards have their own submission route, so a pile of old cards can still be useful if you plan the submission carefully. CQ awards have their own application process and a separate checking system, so something that is confirmed for DXCC isn't automatically accepted for WAZ without the right paperwork or data.

For IOTA, the island group and the reference number matter more than the DXCC entity. Verify that the operation was within the group and that the confirmation details are valid. Some operators work an island and only later realize that the specific group wasn't credited because the QSL listed the wrong operating location.

POTA and SOTA are great for building an activity streak, but keep the QSO logs organized by reference. If you hunt and activate, one ADIF file for everything can get messy. Splitting exports by program, or at least tagging each QSO with the park or summit reference, makes submission to the right system much easier later. And whatever program you're chasing, save a backup of your logbook before any bulk edit, import or upload. Correcting a few bad QSOs by hand is better than discovering the mess after a mass change.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.