APRS Packet Errors for DM2COL-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
20260208151116DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208154117DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208161118DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208164118DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208171119DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208174120DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208181120DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208184120DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208191120DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208194121DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208201122DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only
20260208204123DM2COL-10>APLRG1,TCPIP*,qAC,T2MEXICO:!L4ew]Qs*3& !GLoRa APRS iGate 433.775 MHz, RX only