APRS Packet Errors for EA1P-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
20260209140412	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209142922	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209145428	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209151936	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209154440	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209160954	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209163458	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209170008	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209172513	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209175018	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209181523	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209184028	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M
20260209190538	EA1P-10>APLOX1-1,TCPIP*,qAC,T2SPAIN2:!L9vr^M