APRS Packet Errors for RPTR-970 (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
20260209130408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209133408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209140408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209143408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209150408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209153408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209160408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209163408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209170408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209173408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209180408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR
20260209183408	ZL2UCX-OG>APJIO4,TCPIP,qAC,T2ZL:;RPTR-970 000000z4335.36S/17242.98Er UHF 439.70 DMR