Club Log Explained: Log Uploads, Most Wanted List and OQRS
If you chase DX for more than a few weeks, someone will tell you to “put your log on Club Log”. Club Log is a free online service where amateurs upload their logs to track DXCC progress, compare results with other operators, check whether they are in a DXpedition’s log and request QSL cards. It has become part of the everyday infrastructure of DXing, used by individual chasers, DXpeditions and the logging programs that sit on almost every shack computer.
This guide explains what Club Log does, how to upload your log correctly, how to read your DXCC charts, what the Most Wanted list actually measures, how to use expedition log searches and OQRS, and the mistakes that most often cause confusion. Club Log’s features evolve over time, so for current details always refer to the Club Log website and its help pages.
What Club Log Is and What It Is Not
Club Log is a log analysis and DX tracking service. You upload your log, and it works out which DXCC entities you have worked and confirmed on each band and mode, how you compare with others, and which contacts are still missing. It also hosts logs for many DXpeditions and provides tools for them to handle QSL requests.
Not a confirmation service
Club Log is not an award confirmation system. A contact appearing in both your log and a DXpedition’s log on Club Log does not count towards DXCC by itself. Confirmations for the award come through the channels accepted by the award sponsor, such as Logbook of the World or verified QSL cards. Our guide to LoTW, eQSL and paper QSLs explains those routes. Club Log helps you see where you stand and how to get the confirmations you still need.
Why it became so widely used
The service grew because it answers questions every DXer asks: Which entities do I still need on 30 metres? Am I in that expedition’s log? Which entities are rarest across the community? It does this automatically from your own data, and it can be updated directly from many logging programs.
Uploading Your Log
Everything starts with your log. Club Log accepts logs in ADIF, the standard exchange format supported by nearly every logging program. If you are unfamiliar with it, our article on ADIF files covers the format and common pitfalls.
First upload
- Create an account and register your callsign or callsigns.
- Export your full log from your logging program as an ADIF file.
- Upload the file to the correct callsign. If you have operated under several callsigns, keep each one separate.
- Wait for processing, then review the summary for errors and warnings.
Keeping it up to date
Many logging programs can upload new contacts to Club Log automatically, either immediately after each contact or in batches. This keeps your charts current and, importantly, makes your contacts available for log matching when you want to request QSLs. If your program does not support automatic uploads, upload a fresh export periodically.
Replacing versus adding
Club Log typically lets you either add new contacts to your existing log or replace the whole log with a fresh upload. Replacing is useful after you have corrected errors in your logging program. Read the options carefully before uploading so you do not accidentally duplicate or delete data.
How Club Log Assigns DXCC Entities
A log entry contains a callsign, a date, a band and a mode. To work out which DXCC entity a contact counts for, Club Log uses a database of prefixes and exceptions that maps callsigns to entities over time. Many callsigns do not follow simple prefix rules: special event stations, portable operations, expeditions and historical reallocations all need special handling.
The exceptions data
Club Log maintains detailed data on these exceptions, and many logging programs use the same data to look up entities while you operate. This consistency is one reason Club Log results generally match what your logging software shows. When they differ, the difference often points to an error in your log, such as a contact logged with the wrong date or callsign.
Invalid and questionable contacts
Your upload summary may list contacts that could not be matched to an entity or that fall outside an operation’s known dates. Treat these as prompts to check your log. Busted callsigns, wrong dates and time zone errors are common causes.
Reading Your DXCC Charts
Once your log is uploaded, Club Log presents DXCC charts showing, entity by entity, whether you have worked and confirmed each one on each band and mode. For a DXer this is often the most useful view in the whole service.
Band slots
A band slot is a combination of entity and band, sometimes also mode. Chasing band slots is how many experienced DXers stay motivated after the basic entity count is high. The charts make gaps obvious: an entity worked on 20 metres but never on 40 metres, or confirmed on SSB but not on CW.
Confirmation status
Charts distinguish worked from confirmed. How confirmations are recorded depends on the information in your uploaded log and the options you have set. Keep your logging program’s confirmation fields accurate so the charts reflect reality. For the rules that decide what counts towards the award itself, the ARRL DXCC programme pages are the authoritative source.
League tables
Club Log also offers league tables that rank members by entities worked or confirmed, often grouped by region or club. They are a friendly way to measure progress against peers. Remember that tables only reflect logs people have uploaded and kept current.
Setting goals from the charts
The charts are most useful when you turn them into a short target list. Pick a band where you have many gaps, note the entities that are regularly active from your location, and focus on them for a season. Revisit the list after each upload. Small, specific goals, such as confirming every entity in one continent on a given band, keep DXing interesting long after the obvious entities are in the log.
The Most Wanted List
The Club Log Most Wanted list ranks DXCC entities by how many Club Log members still need them. It is calculated from the uploaded logs of active members, so it reflects actual demand among real chasers rather than opinion.
How to use it
- Prioritise. If an entity near the top of the list is active, drop everything; it may not be on the air again for years.
- Understand rarity. Entities high on the list are usually rare because of access, politics or a lack of resident amateurs, not because nobody tries.
- Plan expeditions. DXpedition teams use the list to choose destinations that will satisfy the most demand.
Limitations
The list is based on Club Log members’ logs. It is a very large sample but not the whole amateur population, and some regions are better represented than others. Use it as a strong indicator, not an absolute ranking.
Expedition Logs, Livestream and OQRS
For DXpeditions, Club Log provides a public log search, charts of activity and, in many cases, an Online QSL Request System.
Checking whether you are in the log
After working a DXpedition, you can search its log for your callsign and see which band and mode slots you are credited with. If a contact you made does not appear, check your own log for errors first. Many expeditions update their logs during the operation, and some provide near real-time updates so chasers can see immediately whether a contact made it into the log. This helps reduce “insurance” contacts that waste the DXpedition’s time.
OQRS
Club Log OQRS is the online system many DXpeditions use to handle QSL requests. Instead of sending a card and return postage by mail, you select the contacts you want confirmed and choose a route offered by the expedition, which may include direct cards, bureau cards or electronic confirmations. Payment and donation options vary by expedition. OQRS reduces errors because it matches your request against the expedition’s log automatically.
Log matching and your uploaded log
Some OQRS options check your request against your own uploaded log. Keeping your Club Log upload current makes these requests smoother and reduces rejections due to mismatched details.
Club Log Features at a Glance
| Feature | What it does | Who uses it most | Tip |
|---|---|---|---|
| Log upload | Stores and analyses your contacts | Every member | Automate uploads from your logging program |
| DXCC charts | Shows worked and confirmed by band and mode | DX chasers | Use them to target missing band slots |
| Most Wanted list | Ranks entities by member demand | Chasers and DXpedition planners | Watch for top-ranked entities becoming active |
| Expedition log search | Confirms whether you are in a DXpedition log | Chasers after working an expedition | Check your own log first if a contact is missing |
| OQRS | Handles QSL requests online | DXpeditions and chasers | Keep your upload current for smooth matching |
| League tables | Ranks members by entity totals | Clubs and competitive DXers | Compare progress with local operators |
Common Mistakes and How to Avoid Them
- Mixing callsigns. Uploading contacts from different callsigns into one log confuses charts and log matching. Keep them separate.
- Wrong time zone. Logs must be in UTC. A log in local time will mismatch expedition logs and fall outside operation dates.
- Stale uploads. An outdated log shows gaps that no longer exist and can delay OQRS requests.
- Treating a match as confirmation. Appearing in an expedition log is useful information, but you still need an accepted confirmation for the award.
- Ignoring warnings. Upload warnings often reveal real errors in your log. Fix them at the source in your logging program, then upload again.
Using Club Log as a Club or Team
Club Log is not only for individuals. Radio clubs can use league tables to run friendly DXCC competitions among members, which is an easy way to keep people active between contests. Seeing a local operator climb the table often encourages others to upload their logs and start chasing band slots. Contest and DXpedition teams also benefit: a shared view of which entities or bands generated the most demand helps plan future operations.
Privacy and what you share
Uploading a log means sharing information about your contacts with a third-party service. Some of that information, such as your appearance in expedition logs or your position in league tables, can be visible to others. Read the service’s privacy settings and choose what you are comfortable sharing. If you operate under several callsigns, decide for each one whether you want it included in public tables.
Club Log in a Modern DX Workflow
A typical workflow ties several tools together. A DX cluster or alert system tells you an entity you need is on the air. You work it and your logging program records the contact. The log uploads to Club Log and to your electronic confirmation service. You check the expedition’s log on Club Log, request a confirmation through OQRS if needed, and your charts update once the confirmation arrives. Our guide to automating DX spot alerts covers the first step of that chain.
The Bottom Line
Club Log turns your log into a clear picture of your DX progress, shows which entities the community needs most, and simplifies the process of confirming contacts with DXpeditions. Upload your log in UTC, keep each callsign separate, automate updates from your logging program and treat warnings as prompts to fix your own data. Use the Most Wanted list to set priorities and OQRS to request confirmations, but remember that award credit still comes from accepted confirmation systems. Used that way, Club Log is one of the most valuable free tools a DXer has.
Frequently Asked Questions
Is Club Log free to use?
Basic use is free, and the service is supported by donations. DXpeditions may ask for payments or donations for QSL cards requested through OQRS.
Does Club Log count for DXCC?
No. Club Log is a tracking and analysis tool. DXCC credit comes from confirmations accepted by the award sponsor, such as Logbook of the World or verified QSL cards.
What does the Club Log Most Wanted list show?
It ranks DXCC entities by how many active Club Log members still need them, based on their uploaded logs. Entities near the top are the rarest in practice.
How do I request a QSL through Club Log OQRS?
Search the expedition’s log, select your contacts and choose one of the confirmation routes the expedition offers. Keeping your own log uploaded helps the request match smoothly.
Why is my contact missing from a DXpedition log?
Common causes are a wrong time or date in your log, a busted callsign on either side, or a log that has not been updated yet. Check your own entry first.
Can my logging program upload to Club Log automatically?
Many logging programs support automatic or batch uploads. Check your program’s settings and enable real-time upload if it is available.