APRS Packet Errors for M0LKS (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
20260208132838M0LKS>APLRG1,TCPIP*,qAC,T2CHILE:!L3S-JO$oHa GLoRa APRS , IO83UM
20260208134339M0LKS>APLRG1,TCPIP*,qAC,T2CHILE:!L3Is+MtSsa GLoRa APRS , IO83UM
20260208135839M0LKS>APLRG1,TCPIP*,qAC,T2CHILE:!L3IsAMtSna GLoRa APRS , IO83UM
20260208144340M0LKS>APLRG1,TCPIP*,qAC,T2CHILE:!L3Is`MtT=a GLoRa APRS , IO83UM
20260208145840M0LKS>APLRG1,TCPIP*,qAC,T2CHILE:!L3IqQMtTCa GLoRa APRS , IO83UM
20260208151340M0LKS>APLRG1,TCPIP*,qAC,T2CHILE:!L3IrMtT.a GLoRa APRS , IO83UM
20260208152840M0LKS>APLRG1,TCPIP*,qAC,T2CHILE:!L3IrMtT0a GLoRa APRS , IO83UM
20260208154341M0LKS>APLRG1,TCPIP*,qAC,T2CHILE:!L3IrpMtSka GLoRa APRS , IO83UM
20260208170204M0LKS>APLRG1,TCPIP*,qAC,T2SYDNEY:!L3S-JO$oHa GLoRa APRS , IO83UM
20260208171705M0LKS>APLRG1,TCPIP*,qAC,T2SYDNEY:!L3S-JO$oHa GLoRa APRS , IO83UM
20260208173206M0LKS>APLRG1,TCPIP*,qAC,T2SYDNEY:!L3IseMtTOa GLoRa APRS , IO83UM
20260208174706M0LKS>APLRG1,TCPIP*,qAC,T2SYDNEY:!L3IsaMtT=a GLoRa APRS , IO83UM
20260208180206M0LKS>APLRG1,TCPIP*,qAC,T2SYDNEY:!L3Is!MtT&a GLoRa APRS , IO83UM
20260208181707M0LKS>APLRG1,TCPIP*,qAC,T2SYDNEY:!L3Is!MtT&a GLoRa APRS , IO83UM