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

Tracking award credits across DXCC, WAS, WAZ, WPX, IOTA, POTA and SOTA: what actually counts as a confirmation?

ci_cover.jpg

Once you chase more than one award, the bookkeeping gets harder than the operating. DXCC, WAS, WAC, WAZ, WPX, IOTA, the CQ DX Marathon, POTA and SOTA all want slightly different things. They differ on what counts as a contact, how it must be confirmed, and who checks it. I'd like this thread to collect the practical points people trip over.

Start with DXCC. Credit goes by entity, not by callsign prefix, and the entity is where the station actually was. Portable and DXpedition callsigns can mislead you here. Entities also change. Deleted entities stay on the separate Deleted list and don't count toward the current total or toward Honor Roll. Whether a QSO counts depends on the date it was made and whether the entity was valid then. Before you trust a spreadsheet, compare it against the current ARRL entity list, not an old copy.

Challenge is a different tally. It counts band-entity combinations, not just entities. A single entity worked on five bands is five credits there. That is why a Challenge chaser's log looks so different from someone building a Mixed total. Check the ARRL's current rules for exactly which bands count.

On confirmations, LoTW is the usual route for ARRL awards, but a QSO only becomes a credit when both sides upload and the records match. Typical failure points are a wrong band, a time outside the matching window, a mode that doesn't fall in the same group, or a certificate whose valid dates don't cover the QSO. Paper QSL cards can still be used for DXCC through authorized checkers, though that route needs more effort. WAS and WAC also accept LoTW, and WAZ and WPX through CQ have their own submission procedures, so read their current rules.

POTA and SOTA work on a different model. Their credit lives in each program's own database. Activators upload logs and hunters or chasers get credit from those logs. A POTA or SOTA contact can also count toward DXCC or WAS, but only if it is confirmed through a DXCC or WAS channel such as LoTW. IOTA has its own reference list and checking process. The CQ DX Marathon counts entities and zones worked in a calendar year and is scored from your submitted log.

Some questions to start us off. How do you keep one master log that satisfies several programs? Do you export ADIF regularly and compare it against LoTW, or rely on what the sites show? And what's the most common reason a QSO you were sure of isn't showing as confirmed?

  • Replies 2
  • Views 29
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

The biggest time saver is treating your own log as the master record and every award site as a downstream check. Export ADIF periodically and keep the original fields intact: station callsign, band, mode, UTC date and time, and the DXCC entity if your logger fills it in. When something is missing in LoTW, the cause is usually in one of those fields.

The station callsign field matters if you operate from more than one location or under different calls. LoTW ties a QSO to a specific callsign certificate and location, so a log uploaded under the wrong location can make a valid contact look like a mismatch. The same goes for grid squares and zones on portable operation. Set the right station location before you sign and upload, not afterward.

Mode is the other common trap. LoTW groups modes for matching, so a digital contact logged under a different digital mode label generally still matches, but a phone QSO logged as CW will not. Cleaning that up in the log before uploading is much easier than untangling it later.

  • Moderators

The deleted-entity and date issue deserves more attention. People see a total on a site, assume it's the whole picture, and then are surprised when the Honor Roll number doesn't match what they expected. Honor Roll is based on current entities, so a contact with a deleted entity can be a nice piece of history but doesn't move you toward it. Check the ARRL's current list and rules for the exact threshold instead of relying on a remembered number.

On POTA and SOTA, I'd keep them mentally separate from the ARRL-style awards. They're excellent for building contacts, and a lot of those stations are portable, which can be a quick way to pick up a state or a rare grid. But the park or summit credit is tracked by those programs, while WAS or DXCC credit still needs a confirmation the ARRL accepts. If you hunt a park and want WAS credit as well, make sure that contact also gets confirmed through LoTW.

One habit that helps is confirming the other station's location before you log it. A portable station might be in a neighboring state or entity, and a log that records the operator's home QTH instead of the actual location can create a credit that never matches.

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.