APRS Packet Errors for PA1MT-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
20250902170914	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)U%S\|
20250902175416	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)X%S\|
20250902180916	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)Y%S\|
20250902182417	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)Z%S\|
20250902183917	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)[%S\|
20250902185417	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)\%S\|
20250902190917	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)]%S\|
20250902192418	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)^%S\|
20250902193918	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)_%S\|
20250902195418	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)`%S\|
20250902203919	PA1MT-10>APLRG1,TCPIP*,qAC,T2SYDNEY:!LoRa APRS\|)c%T\|