APRS Packet Errors for db0s (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
20261002210215	db0s>APRS,TCPIPAC,EIGHTH,qAR,AE7AF:;P-BH2WAV *022102z3.17NP12327.63EG0500D Transmitter(048C)(ON)
20261002210327	db0s>APGHTH,qAR,AE7AF:;A6 *021.4N.67HG2 Tranmer(01LINE)
20261002220013	db0s>APRS,IP*,qAS,AE7AF:;P-DB0LDK5032.277E#PH6DAPNETA Transr23D)(ONLINE
20261002220014	db0s>PS,TCPIP,qAS,AE7AF:;PT 02200z3209.81NP09W#PHDET POCSAG 48C()
20261002220029	db0s>APRS,IP,qAS,AE7AF:;P1SAM 200z5078NP00.64E#P-200DAT POCSTranC(NIE
20261002220148	db0s>APRS,TCPC,FT,qAS,AE7AF:;A2J*022z5224.P0045688E#0200DA Trn48C(
20261002220318	db0s>APRS,IP*,qAS,AE7AF:;O5MTK 2203z4.42NP08.31E#0100DAransmir(05C)LNE)
20261002220324	db0s>PSTPP,IRST,qAR,AE7AF:;KOE2*0203z50N00657.21E#PHE POCSAG Trane(23CD)N)