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: how do you keep it all straight?

ci_cover.jpg

Chasing several awards at once gets messy fast, because the programs define a "credit" differently. A single QSO can count toward a DXCC entity, a CQ zone, a WPX prefix, an IOTA group and a POTA park, and each sponsor wants its own kind of proof. I'd like to compare notes on how people organize this. Please check current rules with each sponsor, since details and fees change.

Here are the distinctions that trip people up most often:

DXCC (ARRL). Credit is by entity, not by country in the everyday sense. The basic award starts at 100 entities, with mode and band endorsements on top, and 5BDXCC is its own track. Deleted entities count toward standard DXCC totals if the QSO was made while the entity was valid, but they do not count toward the Honor Roll or the Challenge. The Honor Roll is based on current entities only. The Challenge is a band-entity point total across the HF bands plus 6 m. That makes a confirmed deleted-entity contact valuable for your base total and worthless for the higher-tier goals.

WAS and WAC. These are simpler in concept, but the details still matter. For WAS, the station you worked has to actually be operating from the state you are claiming, so check the location in the QSO record. For WAC, you need all six continents, and the confirmation just has to match on the basics.

WAZ and WPX (CQ). WAZ counts the 40 CQ zones, which do not map neatly to DXCC entities. Several large entities span more than one zone, so your DXCC log can mislead you about zones. WPX counts callsign prefixes, so a special-event or unusual prefix can add a credit that no entity list would suggest.

IOTA, CQ DX Marathon, POTA and SOTA. IOTA depends on the island group reference, such as EU-005, and the program has its own checking and credit process, so confirm which confirmation types it accepts. The CQ DX Marathon scores entities and zones worked within the calendar year, so only contacts made in that year count. POTA and SOTA are largely database-driven. Activators upload logs and hunters or chasers get credit from matched records, so a paper QSL is generally not the point. Activation thresholds differ, and SOTA's points are tied to the summit.

On LoTW, two things catch people out. First, a confirmation only appears when both stations have uploaded matching QSOs and the band, mode and time agree within the tolerance. Second, the other station's certificate location decides which entity and zone the QSO is tied to. If a DXpedition or portable operator uses the wrong location, or a QSO falls outside the entity's valid dates, the credit may not appear or may not be what you expected.

Questions for the group:

1. What do you use as your master log: LoTW, Club Log, a desktop logger, or a spreadsheet? How do you reconcile them?
2. How do you handle deleted entities and entities whose validity depends on the QSO date?
3. When a contact is unconfirmed, what is your routine for chasing it: a direct card, the bureau, or just waiting for an upload?
4. Do you pursue the Honor Roll and Challenge separately from the lower DXCC endorsements, or do you treat them all as one list?

  • Replies 2
  • Views 23
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

For a master log, I'd pick one source of truth and treat everything else as a derived view. Whichever program you choose, make sure it stores the DXCC entity, CQ zone, IOTA reference, park or summit reference, and the QSL status per sponsor as separate fields. Award credit questions usually come up when those are lumped together. A QSO can be confirmed on LoTW for DXCC and still be unconfirmed for IOTA, or logged for a POTA hunter award with no QSL at all.

On deleted entities, keep them flagged in your own records. Standard DXCC totals can include them, but the Honor Roll and Challenge cannot. If you only track a single "worked entities" count, you can overstate how close you are to the higher awards. A simple column marking current versus deleted solves that.

For unconfirmed contacts, the first step is to check whether the other operator has uploaded to LoTW at all, and whether their certificate location is correct for the date and place of the QSO. Many apparent gaps are just upload timing or a mismatch in band, mode or time. If it's not that, then decide whether a card is worth the postage and delay for that particular entity or reference.

  • Moderators

One practical point on zones. If you're building WAZ from DXCC-oriented data, don't assume entity equals zone. Large countries can straddle several zones, so you need the zone that applies to the station's actual location. If your logger fills the zone from the callsign prefix alone, it can get it wrong for those cases. I'd recheck any zone you're counting on for a last-needed credit before applying.

For the CQ DX Marathon, keep the calendar-year logic in mind. Contacts from last year don't carry over, so some people maintain a separate view filtered by year. That's also a good reason to export your log in ADIF regularly and keep a backup, because LoTW can be slow to confirm and you may want to audit your own records before a deadline.

For POTA and SOTA, check the activation requirements and how the sponsor matches logs. Callsign errors, wrong dates, or a missing reference in your own record are the usual reasons a chaser or hunter credit doesn't show up. Compare your log against the database record before assuming the activator made a mistake.

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.