APRS Packet Errors for sda (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
20260928230120	sda>AEVENTH,qAR,AE7AF:;P-E*4252.438.76W#PDPNET Pmitter(048CNE)
20260929000032	sda>AqAC,SECOND,qAR,AE7AF:;P-KH2PM *290000z3533.90-200DAPNET POCSAG Transmitter(048C
20260929000046	sda>APRSECOND,qAR,AE7AF:;Y *29000047.92NP00108.4PG0010DAPNET POCSAG Titte4C)(OL
20260929000132	sda>APRS,TCPIP,COND,qAR,AE7AF:;M 29018.00NP00607.80E#PHGPNET POCSAG Transmit(ONLI
20260929040024	sda>AqAC,FOURTH,qAR,AE7AF:;P-M0PLL *29026.40N.60W#PHG022SAG Trtter(048C)(
20260929040033	sda>ACPIC,FH,qAR,AE7AF:;P- *2009E#PGPNESAGr(0128LIN