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

Keeping award credit straight: LoTW, paper QSLs, deleted entities and which program counts what

ci_cover.jpg

I'd like to sort out how award credit works across the programs people chase, because the rules differ more than they seem to at first. DXCC, WAS and WAC run through ARRL and LoTW. WAZ and WPX are CQ awards. IOTA has its own reference list and checking process. POTA and SOTA keep their own databases and don't depend on LoTW at all. A QSO that is perfectly good for one can be worthless for another.

The questions I'd like to hear opinions on:

1. How do you handle DXCC entities that are now deleted? They still count toward the basic DXCC award, but as I understand it the Honor Roll is based only on current entities. Does anyone track current and deleted entities separately in their logging software?

2. For DXCC Challenge, is it more efficient to work band-entity slots on purpose, or to let them accumulate from normal operating and then fill the gaps?

3. What are the usual reasons a LoTW match fails when both stations have uploaded? I'm thinking of mode groups, time offset, and the station location set up in TQSL.

4. Does it make sense to run one master log for everything, or should POTA/SOTA logs be kept separate from the DX-award logs?

Please check the current rules on the sponsor's site before relying on anything in this thread. Thresholds, accepted confirmation types and entity lists can change.

  • Replies 2
  • Views 23
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the LoTW mismatches, the TQSL station location is the first thing to check. If the DXCC entity, CQ zone or ITU zone in it is wrong, your upload can look fine and still not match, or it can credit the wrong entity. This matters most if you operate from more than one place. Make a separate station location for each one, and for each callsign if you hold more than one.

After that, check mode and timing. LoTW matches by mode group (CW, phone, data) rather than exact mode, so a phone QSO logged as a digital mode will not match. The time also has to fall within the allowed tolerance, so a log kept in local time or with a bad clock offset will fail quietly. A QSO that is unmatched after a few weeks is usually worth checking against the other station's log if you can see it.

For deleted entities, I'd keep a separate view or report in your logging program that flags which entities are current and which are deleted. DXCC credit depends on the entity as it existed at the date of the QSO. The Honor Roll question is a separate thing, since it looks only at current entities. A QSO with a deleted entity is not wasted for the basic award, but it won't move you toward Honor Roll.

  • Moderators

I'd keep one master log and export from it, rather than splitting logs by program. The programs want different things from the same QSO. POTA expects an ADIF file uploaded to its own system, with the park reference in the right field. SOTA works through its own database, with a summit reference and its own rules for what counts as a valid activation. Neither of those feeds DXCC, so a QSO can be good for several programs at once but still needs to be exported and submitted separately for each. If you work from a park or summit, run the DX-award logging with the correct station location and keep the references in the log.

CQ DX Marathon is different again. It runs on the calendar year, so each year starts from zero and the score is built from entities and CQ zones worked that year. It rewards steady operating more than a one-off big contact, and it is a decent way to track zones you still need for WAZ.

For Challenge, I'd say work the slots you can actually reach. Band-entity credits need propagation to the right place on the right band, and some will only come through a DXpedition. A sensible approach is to build a want list by band, watch spots and cluster activity for those entries, and keep a note of which confirmations are still unmatched. For IOTA and for paper QSL submissions, read the sponsor's current rules on what confirmation they accept before you spend money on cards or postage.

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.