[CQ-Contest] cqww cw spotting report

Tue Dec 1 17:57:47 PST 2009

There were 49440 spots in the database this weekend.  

The database from my node, the dxsummit excel spreadsheet and this 
report will be available for download shortly after this is published 
at http://www.k1ttt.net/logs/2009cqwwcw_spots.zip .

Most spotted DX:

DX		Count
HC8GR		517
9L5A		302
LX7I		262
CR3L		259
6Y1V		244
EA8URL	240
JA3YBK	235
PJ2T		221
ZY7C		213
VK6AA		208
ZM1A		208
B7P		205
EE2W		200
KP2M		200

Busiest spotters:
Spotter	count
K1LZ		748
DK8NC		482
UA4ALI	478
K6III		430
UT7NW		426
RN9S		411
RW4AA/9	406
AD6WL		401
UT7MA		370
K3LR-4	349
NQ4I-3	313
W0AIH		298
RA9A		296
S54A		277
NN3W		276
K1TTT-7	271
KE1FO		258
W3LPL-4	252

----------------------------------------------------------------------

Cheerleader report:

What the columns mean:
Spotter = the spotting station
dx = the dx being spotted
spots = the number of spots the spotter made for the dx
total = the total number of spots the spotter made during the contest
pct = percentage of the total spots the spotter made for just that one dx
station.

spotter	dx		Spotcount	count	Pct
S57O		S52ZW		23		39	58
XU7TZG	XU7ACY	21		21	100
HS8KGG	E21EIC	19		76	25
PB2JJ		PI4KGL	18		18	100
UT7IL		EN500I	16		41	39
LZ2NP		LZ8E		16		25	64
9A5SG		9A1O		15		17	88
S56B		Z33F		14		17	82
SV1HER	CR3L		13		13	100
LZ1KZA	LZ1195IR	13		13	100
UT7L		C91LW		12		21	57
DJ8OG		LX7I		12		154	7
DK8NC		CR3L		11		482	2
VE2XAA	VE2IM		10		23	43
CT1EEC	CT1EEC	10		10	100
KB1RTS	NQ4I		10		10	100

----------------------------------------------------------------------

"Single Spotters" are stations who make only one dx spot in the whole 
contest weekend.  It is obviously fairly unusual for a contest operator 
who is active to make only one spot, many make 10's to 100's of spots 
during the weekend.  It is common for DX'ers to make a single spot for 
a rare dx station then turn off the radio, so lots of single spotters 
for rare stations is common, but they also get lots of contest spots 
from other stations.  The key here is the percentage of spots that are 
from 'single spotters'.  A high percentage can be a sign of the use of 
fake callsigns to spot yourself or a friend that you don't want to look 
like you are cheerleading for... in any case, the use of fake callsigns 
is an obvious sign of someone trying to deceive the world in one way or 
another.

What the columns mean:
DX - the dx station being spotted
Total - the total spots for them in the weekend
All(%) - the total number of single spots and the percentage of the total
dxs(%) - the number of the total spots that came from dxsummit and the 
percentage of the total they are.  These are broken out because it is 
very easy for someone to put in fake callsigns on dxsummit and it has been 
a common source of abuse of the system.

DX		Total	All 		DXS
HC8GR		517	34(6%)	8(1%)
VK9XW		198	29(14%)	6(3%)
A31A		126	24(19%)	3(2%)
TX3A		109	16(14%)	5(4%)
JH3AIU	39	14(35%) 	0(0%)
9L5A		302	14(4%)	6(1%)
A25NW		164	11(6%)	2(1%)
JK2VOC/BA4TB31	10(32%) 	0(0%)
YM3A		82	9(10%)	7(8%)
9J3A		136	9(6%)		5(3%)
6Y1V		244	9(3%)		3(1%)
TF4X		130	9(6%)		3(2%)
DR1A		185	9(4%)		4(2%)
KC1XX		197	9(4%)		3(1%)
3V3S		148	9(6%)		4(2%)

This is happily rather 'clean', anyone abusing dxsummit hid it rather well, 
and there are only 2 others that may need more examination.: JH3AIU and 
JK2VOC/BA4TB have a high percentage of single spots.

-------------------------------------------------------------
JH3AIU single spotter spots:

Spotter	FromNode	Freq
K0BET	K1TTT	14031.5
NO6F	K1TTT	14031.5
K6HJN	K1TTT	14027.4
KL2AX	K1TTT	14027.4
N6EQ	K1TTT	14027.4
VA7MI	K1TTT	14031.5
NS0T	K1TTT	14027.4
NI7A	K1TTT	14031.6
KI5I	K1TTT	14031.6
VE7OP	K1TTT	14031.6
KU0C	K1TTT	14031.6
N8KP	K1TTT	14031.6
UW6TY	K1TTT	14029.5
LZ1XL	K1TTT	14014.2

hmmm, guess he hasn't heard that i can analyze stuff like this...
"K0BET","219.114.173.164","2009/11/29 01:37:11 Connect"
"NO6F","219.114.173.164","2009/11/29 01:27:45 Connect"
"K6HJN","219.114.177.144","2009/11/29 21:37:59 Connect"
"KL2AX","219.114.177.144","2009/11/29 22:54:33 Connect"
"N6EQ","219.114.177.144","2009/11/29 23:19:23 Connect"
"VA7MI","219.114.173.164","2009/11/29 01:30:59 Connect"
"NS0T","219.114.177.144","2009/11/29 21:05:56 Connect"
"NI7A","219.114.173.164","2009/11/28 23:55:38 Connect"
"KI5I","219.114.173.164","2009/11/29 00:09:19 Connect"
"VE7OP","219.114.173.164","2009/11/28 23:24:18 Connect"
"KU0C","219.114.173.164","2009/11/29 00:47:28 Connect"
"N8KP","219.114.173.164","2009/11/28 23:35:35 Connect"
"UW6TY","219.114.168.146","2009/11/28 06:41:21 Connect"
"LZ1XL","219.114.168.146","2009/11/28 07:50:13 Connect"

"NF7K","219.114.173.164","2009/11/29 00:34:53 Connect"
made 2 spots

"K5MN","219.114.173.164","2009/11/29 01:47:59 Connect"
"UA4WN","219.114.173.164","2009/11/29 08:26:06 Connect"
connected but never made a spot

both ip's come back to:
role:         Japan Network Information Center
address:      Kokusai-Kougyou-Kanda Bldg 6F, 2-3-4 Uchi-Kanda
address:      Chiyoda-ku, Tokyo 101-0047, Japan
country:      JP
-------------------------------------------------------------
JK2VOC/BA4TB Single spotter spots:

Spotter	FromNode	Freq	Comment
SP1NND	BD5RV	21026	 
4X4KL		BD5RV	21026	WW-test
DF6PQ		BD5RV	21026	fb
I7PJH		BD5RV	21053	 
DL7CW		BD5RV	14066.8	 
JJ1NJA	BD5RV	7018	 
IW1NQC	BD5RV	21026	WW
HA7SL		BD5RV	21026	test

This one would take action by the sysop of bd5rv to see if he has
ip's for those spotters.

-------------------------------------------------------------

Just some quick notes on interesting things in the dxsummit log:

-------------------------------------------------------------

B4B was spotted by OK2SU, RW9AS, RA9KW, WD7E, and RA0UW from an ip from
Beijing.

-------------------------------------------------------------
ct7/lz3nd had a mixed group of spots by lz's and others from various CT
ip's.

UR4T-@		14110	corect call	CT7/LZ3ND	81.193.229.167
CT7/LZ1WR-@		14103	cqww		CT7/LZ3ND
81.193.229.167
W7VJ-@		14061	cqww		CT7/LZ3ND	81.193.229.167
DL1XX-@		14094.2	corect call	CT7/LZ3ND	81.193.229.167
CT7/LZ1WR-@		14094	cqww		CT7/LZ3ND
81.193.229.167
LZ1PZ-@		14105			CT7/LZ3ND	81.193.63.227
IY7T-@		14118	corect call	CT7/LZ3ND	82.154.130.135
IY7T-@		14093	call corr	CT7/LZ3ND	82.154.131.7
WY6TD-@		14036	cqww		CT7/LZ3ND	82.155.92.249
LZ1EW-@		14093			CT7/LZ3ND	85.244.188.240
CT7/LZ1WR-@		14122			CT7/LZ3ND
85.244.188.240
LZ1FL-@		14132.5.0		CT7/LZ3ND	85.244.188.240
LZ3HH-@		14129			CT7/LZ3ND	85.244.188.240

they kept correcting the call because he was mis-spotted as ft7/lz3nd a
couple times from the same ip's... guess they just couldn't type their own
call.

YM3A had a nice cheering section that included ct7/lz3nd and lz1wr:

OH8DC-@		7005	VERY STRONG	YM3A	81.193.229.167
CT7/LZ3ND-@		7005	DAVAI NIKSAN	YM3A	81.193.229.167
CT7/LZ1WR-@		7005	ASIATIK TURKEY	YM3A	81.193.229.167
LZ1EW-@		7005			YM3A	81.193.63.227
LZ1FL-@		7004.9.0		YM3A	81.193.63.227
LZ1PZ-@		7004.9.0		YM3A	81.193.63.227
LZ3FT-@		7004.7.0		YM3A	81.193.63.227
LZ3KF-@		7004.7.0		YM3A	81.193.63.227
CT1AR-@		7004.7.0		YM3A	81.193.63.227
UA4ALK-@		7004.7.0		YM3A	81.193.63.227
CT7/LZ1WR-@		7004.7.0		YM3A	81.193.63.227
CT1AR-@		7007.7.0	cqww	YM3A	82.154.131.7
CT7/LZ3ND-@		7007.4.0	cqww	YM3A	82.155.92.249
W3EXA-@		7007.4.0	ww	YM3A	82.155.92.249
CT7/LZ3ND-@		7007.4.0	GO-GO	YM3A	82.155.92.249
CT1AR-@		7007.4.0	cqww	YM3A	82.155.92.249
WT6R-@		7007.4.0	cqww	YM3A	82.155.92.249
CT7/LZ3ND-@		7007.4.0	VERY STRONG	YM3A
82.155.92.249

What makes these interesting is the lz3nd and lz1wr spots are from
some of the same ip's used to spot ct7/lz3nd up above.  but the whole
cheering section is from portugual.

-------------------------------------------------------------

DL3VZL was spotted from several calls from a german isp:

JH6SDF-@		14018	wwdx	DL3VZL	80.226.16.80
JH6SDF-@		14018	wwdx	DL3VZL	80.226.16.80
UA0CR-@		14022	wwdx	DL3VZL	80.226.16.80
UA9HA-@		21004		DL3VZL	80.226.21.58
UA0CR-@		21050	ww	DL3VZL	80.226.21.58
PY5HL-@		7026		DL3VZL	80.226.22.61
EI8EA-@		3555	test	DL3VZL	80.226.22.61
UA9ZU-@		21052		DL3VZL	80.226.28.242

-------------------------------------------------------------

most of DM7C's spots from dxsummit probably didn't go anywhere because
he couldn't get the frequency right:
VE3LKM-@	3536.5.0		DM7C	93.210.104.157
EA8AZC-@	3536.5.0		DM7C	93.210.104.157
DL1JGA-@	3535.6.0	CQWW	DM7C	93.210.104.157
DJ4IJ-@	3533.2.0		DM7C	93.210.104.157
DJ4IJ-@	3533.2.0		DM7C	93.210.104.157
DJ4IJ-@	3533			DM7C	93.210.104.157
ZL2QB-@	3518.2.0		DM7C	93.214.190.109
DL1JGA-@	3518			DM7C	93.214.190.109
VE2GKH-@	3549.7.0		DM7C	93.214.190.109
VE3LKM-@	3459.6.0		DM7C	93.214.190.109
EA8AZC-@	3525	cq test	DM7C	93.214.190.109
DH5CM-@	3525	cq		DM7C	93.214.190.109
EA8AZC-@	3525			DM7C	93.214.190.109
DJ6AM-@	3524.9.0		DM7C	93.214.190.109
DJ6AM-@	3524.9.0		DM7C	93.214.190.109
EA8AZC-@	3555	cqing		DM7C	93.214.190.137
DL1JGA-@	356317		DM7C	93.214.190.137
EA8AZC-@	351975		DM7C	93.214.190.137
EA8AZC-@	35195			DM7C	93.214.190.137
EA8AZC-@	351975		DM7C	93.214.190.137

if you are going to cheat you might want to practice first to figure
out how to do it.

-------------------------------------------------------------

David Robbins K1TTT
e-mail: mailto:k1ttt at arrl.net
web: http://www.k1ttt.net
AR-Cluster node: 145.69MHz or telnet://dxc.k1ttt.net