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
20260209155254W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209162254W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209165254W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209172254W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209175254W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209182255W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209185255W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209192255W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209195255W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209202255W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209205255W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS
20260209212256W0RMT-3>APLRG1,TCPIP*,qAC,T2CHILE:=L:E^p3x"la !GLoRa APRS