APRS Packet Errors for dbd (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
20261001110211	dbd>APRS,TCqAC,NINTH,qAR,AE7AF:;P-DL8MG1102z5039.35N.47E#PHG0-2ANET POCAransmitter(13579E)
20261001140146	dbd>APRS,TCPIP,qAS,AE7AF:;0AS 011z4509.P9323.33APNET POE)
20261001150058	dbd>PSTPPAC,SNTH,qAR,AE7AF:;P-HB9S00z4648.58NP00637EG-120DACAG mtterA)(ONLI
20261001150311	dbd>APRCPIPC,SETH,qAR,AE7AF:; *013z4845NP36.6PHG4 POC ranstr(15D)(ONE)