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 412.9 km/s
Aurora 1
Updated 14:00 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

Keeping DXCC, WAS, WAZ and the rest straight: what counts, what doesn't, and where credits go missing

ci_cover.jpg

This thread is for sorting out how the major award programs differ, because the rules overlap just enough to cause confusion. A QSO that is perfectly good for WAS may be useless for DXCC Honor Roll, and a log that scores well in the CQ DX Marathon can still fall short of the confirmation standard for a CQ certificate. Please check every point below against the current rules from ARRL, CQ, RSGB, POTA and SOTA before you pay for an application or rely on a deadline. Rules and fee structures get revised.

Here is a rough map to start the discussion.

DXCC (ARRL). Credit is by entity, not by country in the political sense. Confirmations come from Logbook of The World (LoTW) or paper QSL cards checked by an approved card checker. Deleted entities can still count toward the basic award levels if the QSO was made while the entity was valid, but they do not count toward the Honor Roll or the Challenge. That distinction trips people up. Mixed, CW, Phone and Digital are separate tracks, and band endorsements are a different thing again.

DXCC Honor Roll and Challenge. The Honor Roll is based on current entities only. The usual shorthand is that you need to be within nine of the total current list, and Honor Roll #1 means every current entity. The Challenge is a points total across the HF and 6 m bands, with one point per band per entity confirmed. 60 m is not part of it. The Challenge is a different game from a high Mixed total, so one unconfirmed rare entity on one band can matter more than ten extra QSOs on 20 m.

WAS and WAC. WAS needs all 50 states confirmed, and it can be pursued by mode and by band. WAC needs the six continents. Both are much more approachable than DXCC, but the details of what counts still depend on the administrator's rules.

WAZ and WPX (CQ). WAZ is about the 40 CQ zones, so your own zone logging has to be right. WPX is about unique prefixes, which does not map one-to-one onto DXCC entities. A special-event call or a reissued prefix can give you credit that DXCC would never recognise.

IOTA, POTA and SOTA. IOTA is organised by island groups with its own reference numbers and its own checking process. POTA and SOTA are activity programs where credit is built mostly from uploaded logs, not exchanged cards. A POTA activation generally needs at least 10 contacts within a UTC day. SOTA points depend on the summit and on the activator completing the required number of contacts.

CQ DX Marathon. This one runs by calendar year and resets every January. It is more of a seasonal contest of entities and zones than a lifetime award, so it has different log and verification expectations from the certificate programs.

Questions to get started: what is the most common reason you see LoTW matches fail? How do you decide when a paper card is worth chasing instead of waiting for an upload? And how do you keep one master log organised when each award wants a slightly different list?

  • Replies 2
  • Views 32
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The most common LoTW problem is a mismatch in the details, not the other station refusing to upload. LoTW needs both sides to match on band, mode group and time, and the time tolerance is only about 30 minutes. A bad clock, a wrong date near 0000Z, or a mode logged as SSB when the other side logged it as a digital mode can leave a QSO showing as unmatched.

On your own side, check the station location in TQSL. If the DXCC entity, CQ zone, ITU zone, grid or state or county data is wrong, the signed upload will carry those values forever. That matters for WAS and WAZ credits especially, because the awards read the location data, not just the callsign.

For deleted entities, remember that the QSO date is what counts. Those contacts should be treated as historical. I would keep them in the log with their original entity names and not rewrite them to match today's list, since that is what lets the QSO keep its basic-award value.

  • Moderators

On paper cards, I would only chase one when the entity is hard to confirm another way. The operator may not use LoTW, an old DXpedition may have stopped accepting requests, or the card is the only route to a deleted entity you worked a long time ago. For anything else, LoTW is faster and the record is cleaner. The point of the card is still the same: it has to match the QSO in your log, and for DXCC it has to be checked by an approved checker according to the program rules.

One habit that helps across all these awards: keep a single master log in ADIF and treat each award as a separate report from it, not as a separate log. Then POTA or SOTA uploads, LoTW, Club Log and your own tracking spreadsheet all start from the same data, and fixes only have to be made once.

Also keep the lists separate in your head. A DXCC entity, a WAZ zone, a WPX prefix and an IOTA group are four different questions. A single QSO can answer all four, but it can also answer only one of them.

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.