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
20260208133451	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208134951	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208140451	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208141951	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208143451	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208144951	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208150451	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208151951	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208153451	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208154951	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208160452	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208161952	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208163452	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208164952	XE3EA-10>APLRG1,TCPIP*,qAC,T2PERTH:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208170542	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208172043	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208173543	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208175043	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208180543	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208182043	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208183544	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208185044	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208190544	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA
20260208192044	XE3EA-10>APLRG1,TCPIP*,qAC,T2CHILE:!LCpm@7n9La GIGate LoRa GRUPO APRS MÉRIDA