Dupes in a Contest Analyzer Report: Not Counted as Errors

16 พฤศจิกายน 2026อ่าน 8 นาทีLog checking
Dupes in a Contest Analyzer Report: Not Counted as Errors

Short answer: The Contest Analyzer FAQ answers the question “Are dupes errors?” with a clear no: dupes are listed separately and are never counted as errors. The home page repeats it in the phrase “Dupes are not errors”. For you this means two things. A dupe in your log will not appear as a mistake in the error count, and you can still see how many there were and use that figure to improve your habits. The pricing page adds that a QSO, for the plan limit, is every line of the Cabrillo log, including dupes.

What the site says about dupes

Three statements on the live pages concern dupes. On the home page, under “Only what matters”, the site says that a single doubtful hint never makes an error, that dupes are not errors and that you see a short list, not thousands of warnings. In the FAQ, the answer to “Are dupes errors?” is: No, dupes are listed separately and are never counted as errors. And in the pricing FAQ, “What counts as a QSO?” is answered with: every QSO line in your Cabrillo log, including dupes.

Taken together these statements describe a consistent approach. Dupes are a normal part of a contest log. They are recorded in the log, they count as lines in the file and for the plan limit, and they are displayed in their own place in the report, not mixed with the errors. The report keeps the error list short, and still tells you about the dupes.

What a dupe is, and why it is not an error

A dupe is a QSO with a station that you have already worked on the same band and, depending on the contest, in the same mode. Working a dupe usually earns no additional points, and in many contests the organiser simply ignores it. In some contests dupes may carry a penalty, so the rules should be read. In general, however, a dupe is not a mistake of copying or logging; it is a repeated QSO.

The article on dupes in contest logs explains why it is often better to work a doubtful dupe than to refuse it, and the one on logging dupes versus busted calls explains the reasoning: if you are not sure that the station is a dupe, a quick QSO costs less than the risk of sending a no to a new station. This is why logs contain dupes, and why a good log checker does not treat them as errors.

Why it matters that dupes are separate

If dupes were mixed with errors, the error list would be long, and the real mistakes would be hidden in it. The site explicitly aims at the opposite: you see a short list, not thousands of warnings. Separating the dupes lets you focus on the QSOs where a decision is needed, and treat the dupes as information. You see them when you want to see them.

It also protects you from a common anxiety. After a contest, many operators fear that the dupes in their log will be punished. In most contests they are simply not scored, and the organiser may remove them. A report that does not call them errors lets you look at them calmly. If you want to know the exact treatment of dupes in a particular contest, read the current official rules.

Using the dupe information

Although dupes are not errors, they cost time. Every dupe you work is a few seconds that could have been spent on a new station. In a contest with a high rate, a dozen dupes per hour is a lot. The list of dupes in your report is therefore a measure of your dupe-checking habit. Count them, look at the hours in which they occur and ask whether they were deliberate or accidental.

Deliberate dupes are those you worked because you were not sure or because the other station insisted. Accidental dupes come from a missed check: you did not look at the dupe window, the logger did not warn you, or the call was partly copied. If many dupes are accidental, practise the habit of looking at the dupe indicator before you reply. The article on dupe sheets and worked-before checks explains how to organise the check, and cross-band dupes explained covers the cases in which the same station counts again on another band.

Dupes and the plan limit

The plan limit is expressed in QSOs per log. According to the pricing page, the plans allow up to 3,000, up to 5,000 and unlimited QSOs per log, and a QSO is every line of your Cabrillo log, including dupes. This means that when you decide which plan fits, you should count all the lines of your file, not only the unique QSOs. If your log is close to a limit, check the line count with a text editor or the logger before you upload. The pricing page has the details.

This is a practical point: a log of 2,950 unique QSOs and 100 dupes has 3,050 lines. The difference matters only if you are near a limit, but it is easy to check and avoid a surprise.

Dupes and your corrected file

When you download the corrected Cabrillo file, it contains your edits. The report allows you to edit calls, zones, time and frequency, mark QSOs as checked in your own audio recording and duplicate a QSO line. Dupes that were in your log remain in your log unless you remove them. Whether you should remove them before submission depends on the contest rules and the instructions of the organiser. In most cases the organiser’s software handles them, and removing them is not needed. Check the current rules before you decide, and keep the original file unchanged.

One thing that you should avoid is to delete a dupe in order to hide a busted call. If a QSO looks like a dupe because a call was wrong, the right action is to correct the call. The article on not-in-log causes shows how such errors appear from the other side.

Habits that reduce dupes

A few simple habits keep the dupe count down without slowing you. First, trust your logger’s dupe window and look at it every time before you answer a call. Most programs show whether the station has been worked on the band, and a quick glance costs less than a second. Second, enter the callsign as soon as you have heard it, before you send your exchange, so that the check happens early. On a run, when the same station calls you again, send a short reply such as “dupe” or just log nothing and continue, depending on the contest and your style.

Third, be careful with partial calls. A call that you have only half copied cannot be checked against the log, and a dupe can slip through. Ask for the full call if the rate allows. Fourth, in multi-operator stations, make sure that all computers share the same log in real time, as a station that is worked by one operator and again by another on a different computer is a typical source of dupes. The articles on merging logs from several computers and using a second radio describe the situations in which dupes are likely.

Finally, remember that a few dupes are normal. Some stations call again on purpose, some check an uncertain QSO and some contest rules allow repeated QSOs after a certain time. Do not feel embarrassed by them. Treat the number as a trend: if it falls from one year to the next, your habits are improving.

A short routine for dupes after the contest

  1. Open the dupe list in the report and note the number.
  2. Look at the hours with the most dupes and think about what was happening.
  3. Check a few that look like unusual cases: a call that may have been a busted version of a worked station.
  4. Write one sentence in your notebook about how to reduce dupes next time.
  5. Continue with the error list, which is the part that needs decisions.

The routine takes five minutes and gives you a habit to improve. Over several contests, the number should fall. The year-on-year comparison with your own logs lets you see it.

What else is not an error

Dupes are not the only thing that the report treats with care. A single doubtful hint never makes an error. Serial numbers are not checked, because they change in every QSO. QSOs outside the contest period and outside the band limits for your ITU region are marked, with split QSOs shown as a note, which is a separate category. The error list is reserved for the probable errors, and the rest of the information is displayed in its own place.

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 the supported contests and their log deadlines, see the contests page.

Related reading

The bottom line

Dupes are listed separately and never counted as errors, and they count as QSO lines for the plan limit. Use the dupe list as feedback about your habits, not as a list of mistakes, and put your attention on the real error list.

FAQ

Are dupes errors in the report?

No. The FAQ says that dupes are listed separately and are never counted as errors.

Do dupes count towards my plan limit?

Yes. The pricing FAQ says that a QSO is every QSO line in your Cabrillo log, including dupes.

Should I remove dupes before submitting?

That depends on the rules of the contest. Check the current official rules and keep the original file.

Can a dupe hide a busted call?

Sometimes a QSO that looks like a dupe is a wrong call. Check suspicious ones and correct the call.

#Contest Logging#Contest Statistics#Dupes#Log Checking
Check your contest log before you submit it.ตรวจสอบ วิเคราะห์ และพัฒนาล็อกการแข่งขันของคุณทุกปี
เริ่มตรวจ
จาก LY4A เช่นกัน · ฟรี

ไม่พลาด DX ที่คุณรออยู่อีกต่อไป

LY4A DX Reminder. บอกแอปว่าคุณรอนามเรียกขานใด บนย่านความถี่ใด และในโหมดใด แอปจะเฝ้าดู DX cluster ห้าแห่งอยู่เบื้องหลัง และส่งเสียงเตือนจริงทันทีที่นามเรียกขานนั้นปรากฏ — แม้โทรศัพท์ของคุณจะปิดเสียงอยู่ก็ตาม

  • ฟรี — ไม่มีโฆษณา ไม่ต้องมีบัญชี
  • DXScape, DXSummit, DXHeat, PSK Reporter, RBN
  • 160 m ถึง 70 cm · CW, SSB, FT8, FT4, RTTY
  • iPhone, Android, Windows และ Mac

ly4a.com ↗

สร้างโดยทีมเดียวกัน

เครื่องมืออื่น ๆ จากทีมของเรา

พัฒนาโดย Internet Solutions แต่ละตัวช่วยประหยัดเวลาของคุณในแบบที่ต่างกัน

PR PostRSSระบบโพสต์อัตโนมัติจาก RSS สู่โซเชียลมีเดียโพสต์ใหม่จากบล็อกหรือฟีด RSS ของคุณจะถูกส่งไปยังโซเชียลเน็ตเวิร์ก 66 แห่งโดยอัตโนมัติแพ็กเกจฟรี → T Talkmioแชทสด AI สำหรับเว็บไซต์เว็บไซต์ของคุณตอบผู้เยี่ยมชมได้ 24/7 จากเนื้อหาของคุณเอง ในภาษาของพวกเขาแพ็กเกจฟรี · ไม่ต้องใช้บัตร → AM Ask Mioผู้ช่วย AIแชท เขียนโค้ด ออกแบบ เขียนงาน และค้นคว้า Mio เลือกโมเดลที่ดีที่สุดสำหรับแต่ละงานแพ็กเกจฟรี → AB AI Blog Autopilotระบบอัตโนมัติ AI สำหรับบล็อกและโซเชียลAI เขียนบทความ SEO ยาว 2,000–3,000 คำ และแชร์แต่ละบทความไปยังโซเชียลเน็ตเวิร์ก 60 แห่ง3 บทความแรกฟรี → SA Site AI Auditตรวจสุขภาพเว็บไซต์SEO ความเร็ว SSL ความปลอดภัย และการตั้งค่าอีเมลในรายงานเดียว เรียงตามสิ่งที่ควรแก้ก่อนตรวจครั้งแรกฟรี → SE Site SEO AI Auditการครอล SEO เชิงลึกการครอล SEO เต็มรูปแบบใน 7 ด้าน รวมถึงการมองเห็นในการค้นหาด้วย AI พร้อมรายการแก้ไขที่เรียงตามผลกระทบตรวจครั้งแรกฟรี → RF RSS Feed Creatorฟีด RSS และฟีดสินค้าสร้าง RSS จากหน้าเว็บใดก็ได้ พร้อมฟีดสินค้าสำหรับ Google และ Meta ที่อัปเดตตัวเองแพ็กเกจฟรี → IS Internet Solutionsพัฒนาเว็บและ SEOเว็บไซต์ ร้านค้าออนไลน์ และระบบเฉพาะทาง ออกแบบ สร้าง และดูแลโดยทีมของเราตั้งแต่ปี 2011 →