APRS Packet Errors for XE2XEH-D (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
20250701051158XE2XEH-D>APN100,TCPIP*,qAS,XE2XEH:;BASE 2549.05N/10005.59W/-*QTH Principal [0511z UTC]
20250701051159XE2XEH-D>APN100,TCPIP*,qAS,XE2XEH:;BALT 2539.73N/10016.72W/-*QTH Alterno [0511z UTC]
20250701051200XE2XEH-D>APN100,TCPIP*,qAS,XE2XEH:;SSPC 2539.76N/10016.69W/!*Policia [0512z UTC]
20250701051201XE2XEH-D>APN100,TCPIP*,qAS,XE2XEH:;PCNL 2540.32N/10016.95W/A*Proteccion Civil NL [0512z UTC]
20250701051203XE2XEH-D>APN100,TCPIP*,qAS,XE2XEH:;G42M 2541.32N/10016.29W/,*ASMAC 42 [0512z UTC]
20250701051203XE2XEH-D>APN100,TCPIP*,qAS,XE2XEH:;CSNL 2540.66N/10017.97W/,*ASMAC NL [0512z UTC]