CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] WRTC Calls

To: "cq-contest@contesting.com" <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] WRTC Calls
From: jimk8mr--- via CQ-Contest <cq-contest@contesting.com>
Reply-to: "jimk8mr@aol.com" <jimk8mr@aol.com>
Date: Tue, 11 Jul 2023 16:26:18 +0000 (UTC)
List-post: <mailto:cq-contest@contesting.com>
 I had wondered if in honor of Italy's contributions to modern civilization 
they would be using Roman Numerals in the callsigns, i.e. "I IV III C" rather 
than "I43C".
LXXIII,
Jim   K8MR


    On Tuesday, July 11, 2023 at 12:09:31 PM EDT, ktfrog007--- via CQ-Contest 
<cq-contest@contesting.com> wrote:  
 
  Non-standard two-digit I##x prefix calls starting with I4 were a poor choice. 
Lots of IARU participants are casual contesters and don't follow online 
discussions and info all the time. They have lives otherwise.
Much better call blocks would have been I8#. Skipping I84 and I86. Let's hope 
the UK guys pay attention.

73,Ken, AB1J
    On Tuesday, July 11, 2023 at 12:05:40 PM UTC, jpescatore--- via CQ-Contest 
<cq-contest@contesting.com> wrote:  
 
 The format of the competitor calls was announced in advance, along with the 
call of the spotting station that would put out SSB spots. That didn't prevent 
oodles of busted spots since none of those A4#! format calls was in history 
files or Super Check Partial files - you weren't alone! 
The ARRL log checking stats should be fun to see...
73 John K3TN
Barry WA2VIU said:
> ... Also, maybe I
missed it but I was unprepared for double number calls, and copied I43C as
IV3C. Was there a notice in advance of what format the contest team calls
would be? Would be good to know for next time. I was operating unassisted
and therefore did not look up any of the real-time spotting sites that
would have told me this info during contest.



  
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
<Prev in Thread] Current Thread [Next in Thread>