APRS Packet Errors for XE3EA-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
20260209120558	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209122058	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209123558	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209125058	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209130558	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209132058	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209133558	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209135058	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209140558	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209142058	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209143559	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209145059	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209150559	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209152059	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209153559	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209155059	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209160559	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209162059	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209163559	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209165059	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209170559	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209172059	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209173559	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260209175100	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA