APRS Packet Errors for dbda (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)	Packet
20261001110122	dbda>APRS,TAC,TH,qAR,AE7AF:;P-KCWZ 1101z35NP08355.12W#PHG0110DAPNET POCSTransmer(0)(ONLINE)
20261001110250	dbda>APRSTH,qAR,AE7AF:;P-F6ZBP *011102z4800.38NP00718.E#PHG3230DAPNET POCSAG itter(16B)(ON
20261001140213	dbda>AS,TCPIP,qAS,AE7AF:;P-P 011402z45NP00832.543120DAPNET CSAG Trtter(2)
20261001140219	dbda>APRS,TCPI,qAR,AE7AF:;P-DO2BBC *089NP000200DAOCSAG mitter(NLI
20261001150030	dbda>AS,TCqEVENTH,qAR,AE7AF:;P-VE3S1500z4324.19NP.5W#PHG0-210DAPNET POTansmit48C)(ONLINE)
20261001150220	dbda>APRSPPTH,qAR,AE7AF:;P-F *002z9.75NP02.0#PH60DAT POCSAGanster(16ONL)
20261001150302	dbda>APRS,TCP,AC,SEVE,qAR,AE7AF:;P-DO4 *011z4953.NP14HG011DAPNSAGansme59D)(ONLINE)