(Araucaria) cqww cw spotting report

Terça Novembro 27 22:50:50 BRST 2007

Ronaldo

Você não entendeu o objetivo do Spotting report, feito pelo Dave, K1TTT 
após os grandes contests internacionais. Este relatório aponta as 
estações que teriam feito TRAPAÇA usando o DXCluster.

Veja o exemplo abaixo:

SP8HZZ-@: 7020.6 SN8R 91.94.137.183
ON5ARY-@: 7006.2 SN8R 91.94.137.183
ON5ARY-@: 7035.8 SN8R nice signal 91.94.222.114
ON5ARY-@: 7036.3 SN8R strong signal 91.94.222.114
SP8CTE-@: 7032.2 SN8R 91.94.222.114
SP8GWI-@: 7002.8 SN8R 91.94.222.114
JA4FIQ-@: 7002.8 SN8R good in JA 91.94.222.114
JA4FIQ-@: 7002.7 SN8R fb signal 91.94.222.114
N2HN-@: 7008.2 SN8R 91.94.222.114

address:        PTK-Centertel Sp. z o.o.
address:        Skierniewicka 10a
address:        01-230 Warsaw
address:        Poland

Isso quer dizer que a estação SN8R foi anunciada várias vezes por 
estações diferentes que usaram o mesmo IP (número que identifica 
qualquer computador na Internet). O IP em questão aponta para um 
provedor na Polônia. Portanto, as estações ON5ARY, JA4FIQ e N2HN usaram 
o mesmo computador na Polônia para anunciar a SN8R. Muito estranho, não 
é? Pois isso nada mais é que uma tentativa de encobrir um AUTO-SPOT o 
que é totalmente ilegal.

Para relembrar como o DXCluster pode ser usado de forma LEGAL, reproduzo 
um texto meu escrito há algum tempo que esclarece o que é legal e o que 
é ilegal no uso do DXcluster:

::Usar o DXCluster é Legal

Em alguns contests, existe uma categoria separada para quem usa o 
cluster. Geralmente é chamada de Assisted, ou Assistido. Nesta categoria 
é permitido o uso “passivo” do cluster. Passivo quer dizer, receber 
anúncios indicativo/frequencia via cluster.

Tecnicamente, se, e se somente se, você apenas anunciar no cluster, sem 
olhar os spots, não tem problema - não estará Assistido. Mas ainda nao 
sei como é possível anunciar, sem receber os spots. Se houver tal 
possibilidade, favor me informem.

Todas as categorias Multi-Operador (M/S, M/Two, M/M) podem usar o cluster.

Em qualquer categoria é terminantemente proibido usar o cluster para 
auto-anúncio. Então, voce nao pode anunciar a si mesmo. Se voce está 
fazendo CQ, e anuncia as estações que está trabalhando, indiretamente 
voce está chamando a atenção para aquela frequencia, onde voce está. 
Isso é trapaça!!

No entanto, quando se está S&P, procurando e respondendo aos CQs dos 
outros, é perfeitamente legal - e incentivado - anunciar as estações 
ouvidas/trabalhadas no cluster.

CUIDADO: Alguns programas de Contest tem uma opção chamada “SPOT ALL S&P 
QSOs” que pode ser perigosa. Se esta opção estiver marcada, e se por 
acaso, esquecer de colocar o programa no modo RUNNING, ele vai anunciar 
todas as estações trabalhadas na sua frequencia de chamada. Como isso é 
automático, o operador pode enviar os spots sem saber.

73, Luc
ZY7C Team member
PT7AG (also PY8AZT, PX8C, ZZ8Z)
Já visitou estes sites hoje?

Visite o Portal Uirapuru <http://www.uirapuru.org> Visite o DX Brasil 
Net <http://www.dxbrasil.net>

Ronaldo - PY2NFE escreveu:
> Luc , boa noite.
> Durante o CQWW as estações de PY2IQ, PY2NY, PY4PW, PR7AR, PP1CZ ( essas que 
> eu me lembro) tb foram spotadas no web cluster do OH2AQ
>
> 73
> Ronaldo - PY2NFE
> S. Bernardo do Campo - SP
> Grid: GG66rh
> ----- Original Message ----- 
> From: "Luc, PY8AZT" <py8azt em uirapuru.org>
> To: "Lista Araucaria" <araucaria em araucariadx.com>
> Sent: Tuesday, November 27, 2007 2:11 PM
> Subject: (Araucaria) cqww cw spotting report
>
>
> Relatório de Spots durante o CQWW CW 2007
> Uma única estação brasileira é citada.
>
> -------- Mensagem original --------
>
> Please feel free to forward this to other reflectors, organization lists,
> and individuals that may be interested.
>
> Another big weekend for the spotting network.  49342 spots in the database
> for the weekend.  Peak rates were about 1300 per hour both mornings around
> 14z, and almost 1400 a couple hours before the end.
>
> Most spotted stations:
> DX Count
> 3X5A 753
> HC8N 451
> J3A 418
> D4C 403
> HI3A 353
> PJ2T 308
> PJ4A 308
> ZF1A 304
> KH7X 303
>
>
> Busiest spotters:
> Spotter count
> YU2FG 659
> K3LR-3 574
> K6III 520
> N2NS 469
> W3LPL-4 446
> NQ4I 405
> WB8B 399
> W3LJ 336
> N3AM 322
>
>
> =================================================================
> Cheerleader report
> spotter DX Spots total Pct
> R3GCK D4C 38 148 25
> R3GCK ED8A 28 148 18
> 3B8GT 3B8GT 27 30 90
> R3GCK ZS4TX 23 148 15
> PP5IZ PP5BZ 19 41 46
> UW1GZ UR7GO 19 30 63
> K3CT KP2M 18 277 6
> RT4M S79UU 15 129 11
> HA9RT HA3A 15 16 93
> CO8AJ CO8LY 15 15 100
> HB9EDB YU1ARC 15 15 100
> OM5CW OM5CD 14 14 100
> OE3XOB OE3BCA 14 22 63
> LY1C LY7A 13 127 10
> SV2HRT J42WT 12 12 100
> TA2KI TA2RC 12 12 100
> UA0SJ UA0SBQ 12 13 92
> GM4EIW GM0IIO 12 12 100
> LZ1RGT LZ7J 12 12 100
>
> Thats got to be a new one... R3GCK made the report for 3 different stations.
> He must have had good propagation to Africa.
>
> =================================================================
> Single spotter spots:
>
> DX Total All DXSummit
> 3X5A 753 41(5%) 13(1%)
> XT2SE 106 32(30%) 10(9%)
> C91R 48 19(39%) 8(16%)
> HC8N 451 18(3%) 7(1%)
> HP1AVS 29 18(62%) 18(62%)
> KL7CQ 62 14(22%) 13(20%)
> T88IW 38 14(36%) 4(10%)
> SY1942G 46 13(28%) 7(15%)
> RW3WWW 36 12(33%) 12(33%)
> B4TB 15 12(80%) 12(80%)
> PJ7/DG5XJ 24 12(50%) 2(8%)
> S79UU 239 12(5%) 5(2%)
> VK9CCC 39 11(28%) 5(12%)
> 4L0A 109 10(9%) 3(2%)
> VK9AA 139 10(7%) 2(1%)
>
> Remember on this part that a high percentage of spots by 'single spotters'
> for non-rare expeditions is often a sign that the spotter callsigns are
> being faked in some way.  Big expeditions to really rare places often get
> high percentages of dx hunters who only spot them to brag that they worked
> them, then turn off their radio... High percentages for expeditions or
> really rare stations are normally in the 20-30% range.
>
> Hmmmm... HP1AVS, he was also featured in my CQWW SSB report... This is
> interesting though, he wasn't in the cw contest.  he was spotted by about 30
> different calls from a Panama IP address on 18mhz and 14mhz psk and rtty,
> most with identical comments.
>
> And now on to the dxsummit spots...
> ============================================================================
> =========
> First on the hit parade is B4TB who made the list of single spotter spots...
>
>
> KC2ED-@: 14037 B4TB ww24 221.228.14.14
> W3FPL-@: 14037 B4TB 221.228.14.14
> JA1KIP-@: 14025.5 B4TB 221.228.14.14
> UA3ERD-@: 14066.5 B4TB 221.228.14.14
> RN6BU-@: 21005.8 B4TB WW 221.228.14.14
> K6WPP-@: 14014.5 B4TB cqww 221.228.14.22
> W6KLX-@: 14014.5 B4TB ww 221.228.14.22
> KC6YU-@: 3511.3 B4TB CQWW 221.228.14.36
> W6ADP-@: 7044 B4TB 221.228.14.36
> KJ6G-@: 14046.3 B4TB WW 221.228.14.9
> PY2YS-@: 14046.3 B4TB CQ 221.228.14.9
> W5JB-@: 14046.3 B4TB 221.228.14.9
> W7RR-@: 14046.8 B4TB 221.228.14.9
>
> The IP of course is from China Telecom
>
> ============================================================================
> =========
> Next is RW3WWW, while not getting a real high percentage, its still enough.
>
> DL4CF-@: 1828.2 RW3WWW 82.179.87.139
> K2ASB-@: 7031.6 RW3WWW 82.179.87.139
> DL8RCB-@: 3569.6 RW3WWW 82.179.87.139
> RA3WND-@: 1820.6 RW3WWW 82.179.87.139
> PY3ZZ-@: 7040.9 RW3WW 82.179.87.139
> PY3ZZZ-@: 7041 RW3WWW 82.179.87.139
> DL8RCB-@: 7025.2 RW3WWW 82.179.87.139
> K3BRS-@: 3569 RW3WWW 82.179.87.139
> JH1FSF-@: 14014.6 RW3WWW booming 82.179.87.139
> RW0CL-@: 7013 RW3WWW 82.179.87.139
> RA3EUV-@: 3525 RW3WWW 82.179.87.139
> JA3LRZ-@: 7039.8 RW3WWW 82.179.87.139
> DL8RCB-@: 3517.5 RW3WWW 82.179.87.139
> DM8TA-@: 1830 RW3WWW 82.179.87.139
> K2KF-@: 7017.9 RW3WWW 82.179.87.139
> W8PN-@: 3577.5 RW3WWW CW 82.179.87.139
> N2NF-@: 7055.6 RW3WWW 82.179.87.139
> W0DK-@: 7092.4 RW3WWW 82.179.87.139
>
> Do i even have to check the ip???  well, just to be complete, it comes back
> to Kursk State Technical Univercity.
>
> ============================================================================
> =========
> And yet another one... Don't you just love it when they brag about their
> signal??
>
> SP8HZZ-@: 7020.6 SN8R 91.94.137.183
> ON5ARY-@: 7006.2 SN8R 91.94.137.183
> ON5ARY-@: 7035.8 SN8R nice signal 91.94.222.114
> ON5ARY-@: 7036.3 SN8R strong signal 91.94.222.114
> SP8CTE-@: 7032.2 SN8R 91.94.222.114
> SP8GWI-@: 7002.8 SN8R 91.94.222.114
> JA4FIQ-@: 7002.8 SN8R good in JA 91.94.222.114
> JA4FIQ-@: 7002.7 SN8R fb signal 91.94.222.114
> N2HN-@: 7008.2 SN8R 91.94.222.114
>
> address:        PTK-Centertel Sp. z o.o.
> address:        Skierniewicka 10a
> address:        01-230 Warsaw
> address:        Poland
>
> ============================================================================
> =========
> I guess the concept of a decimal point hasn't made it to kl7 yet... most of
> these probably never made it to your screens because of the bad
> frequencies...
>
> K6VV-@: 3546 KL7CQ cqn 69.178.9.102
> K6VV-@: 702259 KL7CQ cqn 69.178.9.102
> K6VV-@: 702225 KL7CQ cqn 69.178.9.102
> K6VV-@: 702225 KL7CQ cqn 69.178.9.102
> WA6POZ-@: 7022 KL7CQ 69.178.9.102
> K7OK-@: 3543 KL7CQ cqn cq ww 69.178.9.102
> KA6VIO-@: 3532 KL7CQ cq ww 69.178.9.102
> W6OO-@: 3532 KL7DX 69.178.9.102
> KJ5Y-@: 704312 KL7CQ cqing 69.178.9.102
> KJ5Y-@: 7043 KL7CQ 69.178.9.102
> WB6OVC-@: 700843 KL7CQ cqn 69.178.9.102
> W6EET-@: 3510 KL7CQ cqn 69.178.9.102
> K7ZAT-@: 3510 KL7CQ zone 1 69.178.9.102
> K6OO-@: 140356 KL7CQ 69.178.9.102
> K6OO-@: 140356 KL7CQ 69.178.9.102
> K6OT-@: 140327 KL7CQ 69.178.9.102
> K6OT-@: 140327 KL7CQ 69.178.9.102
> K6OT-@: 140327 KL7CQ 69.178.9.102
> W6UY-@: 1403273 KL7CQ 69.178.9.102
> JA1SD-@: 1403273 KL7CQ 69.178.9.102
> JA1CI-@: 140327 KL7CQ 69.178.9.102
> K6II-@: 1406443 KL7CQ 69.178.9.102
> N5DT-@: 1406443 KL7CQ CQN 69.178.9.102
>
> OrgName:    GENERAL COMMUNICATION, INC.
> OrgID:      GENER-72
> Address:    2550 Denali Street
> Address:    Suite 1000
> City:       Anchorage
> StateProv:  AK
>
> ============================================================================
> =========
> This guy wanted to make sure you knew what zone he was in!
>
> EA3KE-@: 7036.5 3G1X WW Z12 206.49.217.33
> I4JFO-@: 7036.5 3G1X Z12 206.49.217.33
> I4JFO-@: 7036.5 3G1X Z 12 206.49.217.33
> EA5GB-@: 7052 3G1X WW Z12 206.49.217.33
> DL4JES-@: 7084.5 3G1X WW Z12 206.49.217.33
> EA5HC-@: 7042.5 3G1X WW Z12 206.49.217.33
> CE1TT-@: 7042 3G1X 206.49.217.33
> CE1TT-@: 7084.5 3G1X ww z12 206.49.217.33
> K3GA-@: 70575 3G1X Z12 206.49.217.34
> 9A7R-@: 7071 3G1X Z12 206.49.217.34
> K8GA-@: 7080 3G1X WW 206.49.217.34
> K8GA-@: 7080 3G1X WW 206.49.217.34
> JH4CU-@: 7024.7 3G1X WW Z12 206.49.217.34
> JH4CU-@: 7024.7 3G1X WW Z12 206.49.217.34
>
> Address:    1 NORTE 461 OF 506
> Address:    VINA DEL MAR, QUINTA REGION 11111
> Country:    CL
>
> ============================================================================
> =========
> And the first of the JT's this time...  Isn't Mongolia rare enough to get
> plenty of spots without helping themselves out this way???
>
> OH3ED-@: 21073 JT1BV ww 203.169.49.183
> DK4RF-@: 14073 JT1BV ww 203.169.49.183
> JT1KAI-@: 28023 JT1BV WW 203.169.49.183
> JT1KAI-@: 28023 JT1BV WW 203.169.49.183
> LZ2GF-@: 21060 JT1BV 203.169.49.183
>
> address:      Sky Plaza 29, Olympic street 14, Ulaanbaatar, Mongolia
> ============================================================================
> =========
>
> Another curious batch of spots from Mongolia.  If you remember my
> suplimental report after the ssb test you might recognize this pattern.  I'm
> sorry i stripped off the times from the dxsummit spots (the ones with the
> -@) but i did manually match them up with the real spot times.  What is
> going on is that someone in mongolia is spotting rare callsigns on the same
> frequency that jt1co is running on, as evidenced by the 'Real' spots
> intermixed below.  Probably an attempt to draw attention to jt1co without
> actually spotting him.
>
> Fake: HA3FG-@: 7003 VQ9R ww 202.179.3.179
> Fake: OH2DR-@: 7051 9U0A 202.179.3.179
>
> Fake: JH5HGT-@: 21012 A52AM 202.179.3.179
> Fake: JH7DSW-@: 21012 9N7JO 202.179.3.179
> Fake: JH7GTR-@: 21012 A52AM 202.179.3.179
> Fake: JH2CFR-@: 21012 S21LU 202.179.3.179
> Real: 21012 11/24/2007 03:14:00 JT1CO JT
>
> Fake: OH2DSE-@: 21004 A52AM 202.179.3.179
> Fake: SP2GF-@: 21004 V85SS 202.179.3.179
> Fake: UU7GV-@: 21004.5 9U0A 202.179.3.179
> Real: 21004.4 11/24/2007 06:59:00 JT1CO
>
> Fake: DL3DR-@: 14004 S21LU 202.179.3.179
> Fake: OH2DR-@: 14004 V85SS CQWW 202.179.3.179
> Real: 14003.9 11/24/2007 08:21:00 JT1CO
> Real: 14004 11/24/2007 09:06:00 JT1CO
> Real: 14004 11/24/2007 09:25:00 JT1CO
>
> had enough??? i have...  here are some more if you want to try to match them
> up to real spots of jt1co...
>
> DL3DR-@: 14098 9N7NO CQWW 202.179.3.179
> JH7DSW-@: 7002 9N7NO 202.179.3.179
> W7HG-@: 7006 9N7JO CQWW 202.179.3.179
> ON4FG-@: 1823.7 S21EA 202.179.3.179
> W5FT-@: 7007 JT1T 579 lp 202.179.3.179
> PY1FR-@: 7025 PY1IAM 202.179.3.179
> DF4CD-@: 3504.5 JT1T 202.179.3.179
> OM5EW-@: 3504.5 JT2C 202.179.3.179
> DL3DR-@: 1826 JT1T CQWW 202.179.3.179
>
> address:      Sq.Sukhbaatar-1
> address:      Chingeltei District
> address:      Ulaanbaatar-210611
>
>
> ============================================================================
> =========
> Why, oh why??  isn't 3b8 rare enough to not have to spot themselves???
>
> RV3BZ-@: 7033 3B8GT FB 196.27.94.12
> 3B8GT-@: 14065 UT5UIA 599 196.27.94.12
> 3B8GT-@: 14065 3B8GT 196.27.94.12
> 3B8GT-@: 14066.5 3B8GT 196.27.94.12
> 3B8GT-@: 14066 3B8GT 196.27.94.12
> 3B8GT-@: 7033 3B8GT 196.27.94.147
> 3B8GT-@: 14066 3B8GT 196.27.94.147
> 3B8GT-@: 7033.8 3B8GT 196.27.94.147
> 3B8GT-@: 7033.8 3B8GT 196.27.94.147
> UA3DEV-@: 7032.5 3B8GT 599 196.27.94.147
> 3B8GT-@: 14021 3B8GT 196.27.94.147
> UA3DEV-@: 14021 3B8GT 196.27.94.147
> UA3DEV-@: 14021 3B8GT 599 196.27.94.147
> RX3FF-@: 7033.6 3B8GT 599 196.27.94.147
> 3B8GT-@: 7033.6 3B8GT 196.27.94.147
> 3B8GT-@: 3566 3B8GT 196.27.94.218
> UA3DEV-@: 3568.5 3B8GT 196.27.94.218
> 3B8GT-@: 3568.5 3B8GT 196.27.94.218
> UA3DEV-@: 14059.3 3B8GT 599 196.27.94.224
> RX3FF-@: 14059.3 3B8GT 599 196.27.94.224
> 3B8GT-@: 14059.3 3B8GT 196.27.94.224
> UA3DTS-@: 14059.3 3B8GT 599 196.27.94.224
> UA3DEV-@: 7036.5 3B8GT 599 196.27.94.224
> SV2HRS-@: 7056.7 7S2E 196.27.94.224
> NF9V-@: 14059.3 3B8GT 599 196.27.94.224
> UA3DEV-@: 14065.7 3B8GT 599 196.27.94.224
> 3B8GT-@: 7038 3B8GT 196.27.94.224
> 3B8GT-@: 7038.5 3B8GT 196.27.94.224
> 3B8GT-@: 7033.2 3B8GT 196.27.94.3
> UA3DEV-@: 14050.7 3B8GT 599 196.27.95.1
> UA3DEV-@: 14053 3B8GT 599 196.27.95.116
> RX3FF-@: 14053.7 3B8GT 599 196.27.95.116
> RX3AX-@: 14003.8 3B8GT 599 196.27.95.137
> UA3DEV-@: 14065 3B9GT 599 196.27.95.137
> RX3FF-@: 7033 3B8GT 599 196.27.95.137
> 3B8GT-@: 7033 UA3DEV 599 196.27.95.137
> RX3AX-@: 7033 3B8GT 599 196.27.95.137
> RX3FF-@: 7033 3B8GT 599 196.27.95.137
> UA3DEV-@: 7036 3B8GT 196.27.95.178
> 3B8GT-@: 7027 3B8GT 196.27.95.178
> 3B8GT-@: 14060 3B8GT 196.27.95.178
> 3B8GT-@: 14060 RU3FF 599 196.27.95.178
> 3B8GT-@: 14005 3B8GT 196.27.95.178
> 3B8GT-@: 7038.5 3B8GT 196.27.95.211
> UA3DEV-@: 7039.4 3B8GT 599 196.27.95.211
> RX3FF-@: 7066.7 3B8GT 599 196.27.95.211
> 3B8GT-@: 7066.7 3B8GT 196.27.95.211
> 3B8GT-@: 3525 3B8GT 196.27.95.211
> 3B8GT-@: 3564.7 3B8GT 196.27.95.253
> UA3DEV-@: 7039 3B8GT 599 196.27.95.253
> RX3FF-@: 7039.1 3B8GT 599 196.27.95.253
> 3B8GT-@: 7039.1 3B8GT 196.27.95.253
> 3B8GT-@: 7050.6 3B8GT 196.27.95.253
>
> address:      6th Floor Edith Cavell St
> address:      Port Louis
> address:      MAURITIUS
>
>
> ============================================================================
> =========
> And then of course there is this group:
>
> K1TTT-@: 7009.4 WP3F 71.101.9.246
> K1TTT-@: 7016.5 WP3F 71.101.9.246
> K1TTT-@: 7016.6 WP3F 71.101.9.246
> K1TTT-@: 14001 K1TTT 71.101.9.246
> K1TTT-@: 1820.7 K1TTT 71.101.9.246
> K1TTT-@: 3519.9 K1TTT 71.101.9.246
> K1TTT-@: 14013 WP3C 71.101.9.246
> K1TTT-@: 7017.8 WP3F 71.101.9.246
>
> Of course we were not putting spots in from dxsummit this weekend.  And the
> IP address comes back to a verizon dsl user out of tampa florida:
>
> pool-71-101-9-246.tampfl.dsl-w.verizon.net
>
> Any node sysops who can check your ip logs and see if you have a real call
> that you can associate with that ip address or the tampa verizon network
> (try searching for 71.101.9.*) please contact me directly.
>
> After i posted that address to a couple email reflectors sunday morning the
> culprit changed spotting nodes and was likely responsible for more that were
> entered from the ea4rh-5 web interface.  Anyone that can contact ea4rh and
> get him to check his web logs for the ip please contact me directly.
>
>
> =================================================================
> I expect the log checkers will ask for the data again this year like they
> have the last couple years.  If you want to do your own analysis or see if
> you have been flagged by any of my checks and just didn't make the hit
> parade listed here you can download the excel and access files, as well as
> the raw data for this summary at:
> http://www.k1ttt.net/logs/2007cqwwcw_spots.zip
> Just please don't ask me to explain it all to you, if you don't know how to
> use complex access queries or excel or how to trace ip addresses I don't
> have time to explain it all to the world.
>
>
>
> David Robbins K1TTT
> e-mail: mailto:k1ttt em arrl.net
> web: http://www.k1ttt.net
> AR-Cluster node: 145.69MHz or telnet://dxc.k1ttt.net
>
>   