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 your award chase organized: DXCC, WAS, WAZ, WPX, IOTA, POTA and SOTA each count credit differently

ci_cover.jpg

Chasing several awards at once gets messy because each program has its own idea of what counts as a confirmed contact. A QSO that is a clean credit for DXCC may be useless for IOTA or SOTA unless you log one extra detail. Here is a rough map of the differences, and I'd like to hear how others keep it straight.

DXCC (ARRL). The base award is 100 entities confirmed, with Mixed, Phone, CW and Digital variants plus band endorsements. The entity list is not the same as countries on a map, and it changes over time. Deleted entities still count toward the basic award if you confirmed them while they were valid, but they do not count toward the Honor Roll or Challenge. The Honor Roll is measured against the current list, so a new entity can change what you need. Challenge is a band-entity point total across the eligible bands, so one entity on 20 m and 15 m is two points. Check the ARRL's current rules for exact thresholds and band lists.

WAS and WAC. Worked All States is 50 states, and many people finish it quickly on LoTW. WAC is the six continents, which is easy in principle, but the band and mode endorsements are where the real work is. Both are better planned by band and mode from the start than sorted out later.

CQ WAZ and WPX. WAZ is built on the 40 CQ zones, and zone boundaries trip people up. Confirm the zone for the station you worked, not just the entity. WPX counts unique prefixes, so special-event and unusual prefixes can matter. CQ's rules decide which confirmation types they accept, and that has changed over the years, so read the current page before sending anything.

CQ DX Marathon. This one is tied to the calendar year. Your score combines entities and zones worked in that year, so everything starts over each January. It is a different mindset from lifetime awards, because a rare one worked in December counts for that year only.

IOTA. Each island group has a reference such as EU-005, and you need the reference logged, not only the entity. Many groups share an entity, and some entities contain several groups. Check which confirmation methods the program currently accepts.

POTA and SOTA. These work differently from classic QSL awards. Hunters and chasers are credited from the activator's uploaded log, and there are no cards or LoTW matching involved. Your own log still has to match the activator's: call, date, time, band and mode. A typo can mean no credit, and often nobody notices until the totals are off.

LoTW notes. Matching depends on both stations uploading and agreeing on band, mode group and time, with some tolerance. Your certificate must be tied to the correct callsign and DXCC entity. If you operate from another entity, the certificate and station location details need to match where you actually were. A mismatched location is one of the most common reasons for a QSO that looks fine but never matches or earns credit.

Questions for the thread: do you keep one master log and export for each program, or separate logs per award? How do you handle QSOs with deleted entities, or contacts you aren't sure were logged with the right entity or zone? And do you still bother with paper QSLs for anything?

  • Replies 2
  • Views 50
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

A single master log with good fields is the approach that makes the most sense to me. The main reason is that most of the awards you list draw on the same few pieces of data: call, date and time in UTC, band, mode, and then program-specific extras. For IOTA that means the island reference, for POTA and SOTA the park or summit reference, and for WAZ the CQ zone. Many logging programs can store these in ADIF fields, so you can export for each program without retyping. Check that your software populates the DXCC entity field using the date of the QSO, since entity status depends on when the contact happened.

For deleted entities, I would record them as normal contacts and never worry about them for the Honor Roll or Challenge, since those use the current list only. The one trap is assuming that an old confirmation can be moved onto a successor entity. It cannot, because the successor is a separate entity and needs its own contact.

Paper cards are still worth keeping for a few things. Some operators and expeditions do not use LoTW, and a card can be the only route to credit for a rare one. For routine contacts, uploading to LoTW and checking the matches regularly is much less work.

  • Administrators

One practical thing to add is to audit your own LoTW setup before you start counting credits. The usual causes of missing matches are boring ones: the wrong grid square or CQ/ITU zone in the station location, a certificate for a different callsign, or a mode that falls in a different group on the other end (for example, a digital contact logged as a phone mode). When a QSO shows as uploaded but unmatched, compare the other station's band, mode and time as they appear in your log before assuming they never uploaded.

Also keep the programs separate in your head. A SOTA or POTA contact needs the reference and the right log timestamp, but it earns you nothing toward DXCC unless the contact also happens to be confirmed through a DXCC-accepted route. The reverse holds as well. A DXCC-confirmed contact does not count for an activator award because it was never logged against a reference.

If you are aiming for Honor Roll or Challenge, compare your confirmed list against the current ARRL entity list on a schedule, because new entities and deletions change the targets. And if you are thinking about the Marathon, remember that it works on a calendar year and plan your operating around that.

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.