APRS Packet Errors for W0RMT-3 (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
20260208145239W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208152240W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208155241W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208162241W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208165241W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208172241W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208175242W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208182242W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208185242W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208185320W0RMT-3>APLRG1,WIDE1-1,qAR,W3JCE-40:=L:E^p3x"la !GLoRa APRS
20260208192243W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208195244W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260208202243W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS