APRS Packet Errors for EA1GLY-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
20260208150837EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208153837EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208161037EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208163837EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208170838EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208173838EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208181038EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208183838EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208190838EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208193838EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208201039EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro
20260208203839EA1GLY-10>APLOX1,TCPIP*,qAC,T2UK:!L9(zZMSuy& XLora iGate Burgos Centro