APRS Packet Errors for 9M2COD-2 (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
20260208144501	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#l!=\|
20260208151002	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#m!=\|
20260208153502	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#n!=\|
20260208160002	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#o!=\|
20260208162502	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#p!=\|
20260208165003	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#q!=\|
20260208171503	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#r!=\|
20260208174003	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#s!=\|
20260208180503	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#t!=\|
20260208183003	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#u!=\|
20260208185503	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#v!=\|
20260208192004	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#w!=\|
20260208194504	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#x!=\|
20260208201004	9M2COD-2>APLRG1,TCPIP*,qAC,T2BC:=LM+ggh:!La !GLoRa N9 APRS Team\|#y!=\|