APRS Packet Errors for XE3JR-10 (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
20260209121512	XE3JR-10>APLRG1,TCPIP,qAC,T2PERTH:!LDaAt5H_Xa G73 4 ALL\|#%h\|
20260209124512	XE3JR-10>APLRG1,TCPIP*,qAC,T2PERTH:!LDaAt5H_Xa G73 4 ALL\|#+%e\|
20260209131512	XE3JR-10>APLRG1,TCPIP*,qAC,T2PERTH:!LDaAt5H_Xa G73 4 ALL\|#,%`\|
20260209134512	XE3JR-10>APLRG1,TCPIP*,qAC,T2PERTH:!LDaAt5H_Xa G73 4 ALL\|#-%c\|
20260209141512	XE3JR-10>APLRG1,TCPIP*,qAC,T2PERTH:!LDaAt5H_Xa G73 4 ALL\|#.%a\|
20260209144512	XE3JR-10>APLRG1,TCPIP*,qAC,T2PERTH:!LDaAt5H_Xa G73 4 ALL\|#/%d\|
20260209151512	XE3JR-10>APLRG1,TCPIP*,qAC,T2PERTH:!LDaAt5H_Xa G73 4 ALL\|#0%`\|
20260209154512	XE3JR-10>APLRG1,TCPIP*,qAC,T2PERTH:!LDaAt5H_Xa G73 4 ALL\|#1%c\|
20260209161511	XE3JR-10>APLRG1,TCPIP*,qAC,T2CHILE:!LDaAt5H_Xa G73 4 ALL\|&R%c\|
20260209164511	XE3JR-10>APLRG1,TCPIP*,qAC,T2CHILE:!LDaAt5H_Xa G73 4 ALL\|&S%e\|
20260209171511	XE3JR-10>APLRG1,TCPIP*,qAC,T2CHILE:!LDaAt5H_Xa G73 4 ALL\|&T%^\|
20260209174511	XE3JR-10>APLRG1,TCPIP*,qAC,T2CHILE:!LDaAt5H_Xa G73 4 ALL\|&U%a\|