CQ-Contest
[Top] [All Lists]

[CQ-Contest] Skimmer accuracy...

To: <cq-contest@contesting.com>
Subject: [CQ-Contest] Skimmer accuracy...
From: "Shane Mattson-->K1ZR" <k1zr@comcast.net>
Date: Tue, 19 Feb 2013 10:06:28 -0500
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
I'm starting a new thread for increased visibility to this issue.

 

This is by no means a skimmer bashing post, so please don't go there..

 

I'm just curious if others have observed the following:

 

Just for kicks I performed a RBN spot search for my call and the following
spots came up during a period of time that I was QRT.  I did not operate at
all on Sunday.

 

de    dx    freq  cq/dx snr   speed time

K3LR  K1ZR 28005.3     CW CQ 13 dB 32 wpm      2042z 17 Feb

K3LR  K1ZR 14046.6     CW CQ 24 dB 31 wpm      2014z 17 Feb

KM3T  K1ZR 14046.6     CW CQ 15 dB 33 wpm      2011z 17 Feb

VE2WU K1ZR 14046.6     CW CQ 20 dB 31 wpm      1927z 17 Feb

K8ND  K1ZR 21006.9     CW CQ 8 dB  32 wpm      1743z 17 Feb

NY3A  K1ZR 28062.4     CW CQ 28 dB 31 wpm      1654z 17 Feb

K2DB  K1ZR 7020.5      CW CQ 10 dB 29 wpm      0855z 17 Feb

K2DB  K1ZR 7020.4      CW CQ 11 dB 30 wpm      0753z 17 Feb

K3LR  K1ZR 3510.3      CW CQ 26 dB 29 wpm      0207z 17 Feb

 

Perhaps the skimmers misinterpreted a like-call sign?  I'm not excited about
seeing my call detected and spotted during a period for which I was QRT.  An
issue like this emphasizes the importance of double checking the call sign
for accuracy before logging a point and shoot qso.

 

Could someone within the RBN domain provide some insight as to how to
address an issue like this?    

 

-Shane

 

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

<Prev in Thread] Current Thread [Next in Thread>