Topband
[Top] [All Lists]

Re: Topband: Contest dupes

To: "Jon Zaimes, AA1K" <jz73@verizon.net>
Subject: Re: Topband: Contest dupes
From: Jim Clymer <ws6x.ars@gmail.com>
Date: Mon, 26 Jan 2026 12:56:38 -0500
List-post: <mailto:topband@contesting.com>
Hi Jon,
Thanks for posting this. I agree 100%. When condx are spotty - QSB, etc. -
it's so much more efficient to just assume they copied my call incorrectly
the first time, and work them again. I know I was a DUPE at least twice in
this contest. Once, I wasn't paying attention, and once I fat-fingered the
call the second time around.
The ones that puzzle me though, are the loud stations that call me, I log
the Q, and then the station calls me again 2 minutes later. Odd!!
Jim - WS6X

On Mon, Jan 26, 2026, 12:22 PM Jon Zaimes, AA1K via Topband <
topband@contesting.com> wrote:

> Sometime during the second night of this weekend's CQ 160 meter CW
> contest, I answered a W station that was calling CQ. They came back with
> "dupe" though they were not in my log. I said "no" and sent a report.
> They came back with "already worked" and didn't send me a report.
> I repeated "not in log" and sent a report. They came back with a time that
> I was apparently in their log. But they were not in my log.
> Since it was a slow period I persisted and they finally sent me a report.
> But this fellow wasted far more of both of our time than if he had just
> worked me when I called. There is no penalty for working a dupe -- the log
> checkers just ignore duplicates.
> Had I not persisted, however, this W station would have been penalized
> since his alleged QSO was not in my log.
> So folks, if someone calls you and you think it is a dupe, just work 'em
> again. They may have actually been working someone else, or flubbed entry
> on the keyboard of your callsign. Just log it a second time if you think it
> is a dupe.
>
>
> 73/Jon
>
> Jon P. Zaimes, AA1K
>
>
_________________
Searchable Archives: http://www.contesting.com/_topband - Topband Reflector
<Prev in Thread] Current Thread [Next in Thread>