APRS Packet Errors for XE1ZKC-20 (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
20260208151250XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208152750XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208154250XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208155750XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208161250XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208162750XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208164250XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208165751XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208171251XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208172751XE1ZKC-20>APLRG1,TCPIP*,qAC,T2VAN:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208174249XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208175749XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208181249XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208182749XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208184249XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208185749XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208191249XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208192750XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208194250XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208195750XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208201251XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208202751XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208204251XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl
20260208205751XE1ZKC-20>APLRG1,TCPIP*,qAC,T2MCI:!LD_m{5K0ea GLoRa APRS iGate, in Nezahualcoyotl