APRS Packet Errors for EA6VQ-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
20260209110946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209113946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209120946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209123946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209130946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209133946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209140946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209143946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209150946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209153946EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209160947EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN
20260209163947EA6VQ-10>APLRG1,TCPIP*,qAC,T2SPAIN:!L:N;9O/@pa GLoRa APRS iGate JM19HN