CQ WW DX CW and the 48-Hour Log Deadline: A Timeline

November 18, 20268 min readContest calendar and rules
CQ WW DX CW and the 48-Hour Log Deadline: A Timeline

Short answer: The Contest Analyzer contests page lists CQ WW DX CW from 28 November 2026, 00:00 UTC, to 29 November, 23:59 UTC, with a log deadline of 48 hours. Because 48 hours is short, plan the check in advance: export the Cabrillo file straight after the contest, upload it at once, review the short list of QSOs worth a second look in a few focused sessions, download the corrected file and submit with a margin. Always read the current official rules for the exact deadline and submission method.

What the contests page shows

The contests page lists 22 contests with their mode, start and end in UTC and the log deadline. For CQ WW DX CW, the row says CW, start 28 November 2026 at 00:00, end 29 November at 23:59 and a log deadline of 48 hours. The page adds that dates are calculated from each contest’s rules, and every row has an “Upload log” link. Compare it with other contests on the page: WAE DX RTTY has 7 days, the 9A DX Contest has 8 days, the Stew Perry Topband Distance Challenge has 14 days and the ARRL International DX contests have 7 days. A 48-hour deadline, as for the CQ WW family, is one of the shortest on the list.

The article on log submission deadlines explains why deadlines differ, and the known rule for CQ WW is that logs are due 48 hours after the end of the contest. Because the exact wording and the way the time is counted come from the organiser, check the current official rules, for example on the contest’s own website, before you plan to the minute.

The timeline in outline

If the contest ends on Sunday 29 November at 23:59 UTC, a 48-hour deadline means that the log must arrive by about the same time on Tuesday 1 December. That is only two working days for many people, and one of them may be a day on which they must be at work. A simple outline is: Sunday night, save and back up; Monday morning, export, upload and review; Monday evening, correct and download; Tuesday morning, submit; Tuesday evening, spare. The margin in the last step is intentional.

The times above are examples; use your own time zone and your own schedule. In the time zone of Europe, the end of the contest is late at night on Sunday for some countries and early on Monday for others, so work out the local time of the deadline in advance, and write it in your calendar.

Sunday night: the last hour and the first minutes after

In the last hour, keep the log tidy and avoid risky changes. When the contest ends, stop at once if your category requires it, save the log and make a backup. Export a Cabrillo file immediately, while your memory is fresh and the software is still in the same state. Do not edit the file. If you are very tired, leave the upload for the morning, but do the export now, because a corrupted database or a crash is more likely when you are tired.

Check the header in a text editor: callsign, category, band, mode and power. The article on the Cabrillo header lists the fields. Then go to sleep. A good night’s rest makes the review much better than a long session at four in the morning. The article on the CQ WW CW final-week checklist includes a reminder to plan the day after the contest.

Monday morning: upload and let the check run

With a rested mind, open Contest Analyzer, choose CQ WW DX CW and the year and upload the file. The home page describes the process: the log is checked in the background, progress is shown live in My logs, and the report appears as soon as it is ready. Contest Analyzer works with Cabrillo from N1MM Logger+, DXLog and Win-Test, and the FAQ says that any Cabrillo 3.0 file is accepted. If you have not yet verified your callsign in your account, do it before the contest, since a log can be checked only for a verified callsign, as the FAQ explains, and see why your callsign is verified.

While the check runs, make a cup of coffee, read your own notes from the contest and find your recording if you have one. The article on background checking and live progress suggests ways to use the waiting time.

Monday: review the short list

When the report appears, read the summary and then work from the strongest suggestions to the weakest. The check covers every callsign and every zone against official license databases and several independent reference sources and shows only the few QSOs worth a second look. For a CW contest, many doubtful rows will be suffixes and characters that sound or look alike, as in the article on confused CW characters. For zones, remember that CQ zones are part of the CQ WW exchange, and the article on the exchange and zone in CQ WW CW goes through cut numbers.

You can edit calls, zones, time and frequency right in the report, mark QSOs as checked in your own audio recording and duplicate a QSO line. Dupes are listed separately and are not errors. QSOs outside the contest period and outside the band limits for your ITU region are marked, with split QSOs shown as a note. Take two or three sessions of forty minutes with breaks. Do not try to settle every row; decide on what you can support and leave the rest as logged.

Monday evening: download and read the file

When the review is finished, download the corrected Cabrillo file. Open it in a text editor and check the header, the first and last QSO lines and the line count. Compare the number of QSOs with your records. Save the file with a clear name, and keep the original and the corrected files in the same folder. The article on making a corrected Cabrillo file before you submit contains a final checklist.

Read the rules once more for the submission method and any special requirements, such as the format of the file name or an accompanying form. The rules of each contest define how logs are sent, and the article on submitting a Cabrillo log describes the usual routes in general terms.

Tuesday: submit with a margin

Submit the log in the morning, not in the last hour. Servers may be busy, an upload can fail and rules may ask for extra information. After the submission, keep any confirmation message and a copy of what you sent. If the organiser’s system sends an automatic reply that reports problems, read it carefully and fix the file if necessary; the article on log robot error messages explains typical replies. If you receive no confirmation within a reasonable time, check the rules for how to confirm that the log arrived.

When the log is submitted, relax. You can still use the report’s statistics, with rates, QSOs by hour and band, countries, continents, CQ and ITU zones, WPX prefixes, distance, beam heading, breaks and off time, to write your own review. Note that in CQ WW the off time of a single operator counts only for breaks of at least 60 minutes, according to the current rule, so your breaks and off time view is worth a look.

If something goes wrong

With a short deadline, plan for the unexpected. If the upload is slow or the report shows an unexpected problem, do not panic. A file that does not open, a header that is wrong or a log of the wrong contest can be fixed by exporting again from the logger, which is why you keep the original database. If you cannot resolve a problem, write to the address on the contacts page with the contest name and a short description. If the problem concerns the submission to the organiser, follow the instructions in the rules; organisers often have a contact address for such cases.

The worst plan is to leave everything for the last evening. If something fails then, there is no time to react. The second-worst plan is to rely on memory for the deadline. Put the exact time in your calendar, with an alarm for the evening before and another in the morning.

If you have a very busy schedule

Not everyone can set aside two days. If your work schedule is tight, compress the plan: export on Sunday night, upload before work on Monday, and review in the evening in one or two sessions. Submit on Tuesday morning before work. The main point is to leave the upload as early as possible, because the check runs in the background while you are busy. And decide in advance how much time you will give to the review, so that you do not spend it all on rows that cannot be settled.

For a club or a team, share the plan in advance, as in the article on club and team logs. Each member has his or her own account and verified callsign, and logs are private, as the FAQ states. A reminder on Monday morning helps everyone to meet the deadline. For other contests and their dates, see the contests page.

Related reading

The bottom line

A 48-hour deadline is manageable with a plan. Export on the night, upload in the morning, review in focused sessions, download and read the corrected file and submit on the second morning, leaving the second evening as a safety margin. Always take the exact deadline and method from the current official rules.

FAQ

When does CQ WW DX CW take place this year?

The contests page lists 28 November 2026, 00:00 UTC, to 29 November, 23:59 UTC. Confirm in the official rules.

What is the log deadline?

The page shows 48 hours. Check the organiser’s current rules for the exact time and method.

Can I upload before I have time to review?

Yes. Uploading early lets the check run in the background, and you can review later.

Do I need to verify my callsign first?

Yes, a log can be checked only for a verified callsign in your account. Do it before the contest.

#Contest Calendar#Corrected Cabrillo#CQ WW DX#CW Contesting#Log Deadlines
Check your contest log before you submit it.Check. Analyse. Improve your contest log every year.
Start checking

More from the blog

All articles →
Also from LY4A · free

Never miss the DX you are waiting for.

LY4A DX Reminder. Tell it which callsign you are waiting for, on which bands and in which mode. It watches five DX clusters in the background and raises a real alarm the moment that callsign shows up — even while your phone is silenced.

  • Free — no ads, no account
  • DXScape, DXSummit, DXHeat, PSK Reporter, RBN
  • 160 m to 70 cm · CW, SSB, FT8, FT4, RTTY
  • iPhone, Android, Windows and Mac

ly4a.com ↗

Made by the same team

More tools from our team

Built by Internet Solutions. Each one saves you time in a different way.