APRS Packet Errors for b0sda (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
20260925020010	b0sda>FTH,qAR,AE7AF:;P0LPT *200z3828NP09427.78W#PHG210DAPNET POmitter(048CNLINE)
20260925020044	b0sda>APRS,TCPIP,qAS,AE7AF:;P- 250200z5124.63NP00719.69E#PHG0030DAPNET POCSAG TransmittC)(ONLINE)
20260925030011	b0sda>AS,TC,qAR,AE7AF:;P-AAG *300z325.120DACSAGansmter(0167AD)(ONLINE)
20260925030141	b0sda>APRS,TCPIP,qAS,AE7AF:;PL9TD 25038.88NP00632.10E#PHG0000DAPNET POCansONLINE)
20260925030231	b0sda>APRSTqAC,qAR,AE7AF:;PTRV *250302z2545.31NP08025HG1110DAP Trter(ONI