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 credit across DXCC, WAS, WAZ, WPX, IOTA, POTA and SOTA: where do the rules actually differ?

ci_cover.jpg

Many of us end up with one log feeding half a dozen award programs, and each program handles confirmation differently. This thread is for comparing notes on where the rules diverge and what that means for how you keep your log. Details change, so check each sponsor's current rules before you submit anything.

Here is a rough map. DXCC (ARRL) works from the current entity list and counts confirmed entities by Mixed, mode and band. Confirmations come from LoTW or from paper cards checked by an approved card checker. The Honor Roll only counts current entities. Deleted entities still count toward your basic DXCC total but are separate from the Honor Roll, and they don't help with the Challenge. The Challenge counts band-entity credits, so the total grows with every new band slot, not just every new entity. WAS (ARRL) and WAC are simpler targets, but they have their own endorsement categories.

CQ's programs use different units. WAZ counts the 40 CQ zones, not entities, and Five Band WAZ makes you cover those zones on multiple bands. WPX counts prefixes, which means a station can be a new prefix without being a new entity. The CQ DX Marathon resets every calendar year and scores entities and zones, so a contact only counts toward the year it was made.

IOTA (RSGB) uses island group references such as EU-005 rather than entities. Many island operations don't line up neatly with DXCC entities, so a reference can be new for IOTA while being a dupe for DXCC, and the reverse. POTA and SOTA are a different kind of program. They work from their own databases and activation rules, not from QSL cards or LoTW matching. A POTA activator logs and uploads to the program's system, and a hunter's credit comes from the activator's log. SOTA has its own point system for activators and chasers, with an activation requirement before the points count.

A few questions to get started:

1. How do you handle LoTW matching when the other station has the wrong band, mode or time in their upload?

2. Do you keep a separate list of deleted entities you've confirmed, or do you rely on the ARRL account's tallies?

3. For paper QSLs, when is it worth getting a card checked rather than chasing the LoTW upload?

4. Do you use one master log with filters, or separate logs per program?

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On LoTW matching: a QSO only becomes a credit when both sides have uploaded and the details match closely enough. That means call, band, mode group and time within the tolerance. The things that most often block a match are a wrong band after a QSY, a mode logged as SSB on one side and a digital mode on the other, and the other station's certificate being tied to a different location or entity. If you can see that the other station is a regular LoTW user and the QSO still hasn't matched, check your own record first, because that is the half you control. Make sure your station location in the upload is set correctly. For DXCC the location matters, because the entity is taken from the certificate's location, not from the call prefix alone.

For deleted entities, I would keep them in a separate view of your log regardless of what the ARRL tallies show. They don't count toward the Honor Roll, so mixing them in with current entities can make your Honor Roll progress look better than it is. Having them separate makes the gap obvious.

  • Administrators

I'd also think about how the programs treat the same QSO differently, because that is what trips people up when they use one log for everything. A contact with an island station on a spare band could be a new band-entity for the Challenge, a new reference for IOTA, a new prefix for WPX and a new CQ zone for the Marathon, or none of those. Filtering by program is easier if your logging software stores entity, CQ zone, IOTA reference, and POTA or SOTA references as separate fields instead of free text in the comment.

For POTA and SOTA, the key difference is that nobody checks a QSL card. Credit depends on the activator's upload and on meeting the activation threshold. It is worth confirming the threshold and any logging rules on the program's own site, because they are updated separately from the DX award rules. I wouldn't carry assumptions from one program into another. A paper QSL that is good for DXCC does nothing for a POTA hunter award, and the reverse is also true.

On paper cards: it generally makes sense when the station doesn't use LoTW or when the entity is rare enough that you don't want to depend on an upload that may never happen. Check the current card-checking and submission rules first, since the process has changed over the years.

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.