APRS Packet Errors for EA4XA-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
20260209120843EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209123847EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209130852EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209133856EA4XA-10>APLOX1-1,qAR,EA4URC-13:!L:6pAMwiB& XLora Tracker/iGate
20260209134056EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209140859EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209143907EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209150910EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209153915EA4XA-10>APLOX1-1,qAR,EA4URC-13:!L:6pAMwiB& XLora Tracker/iGate
20260209154118EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209160920EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209163924EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209170928EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260209173940EA4XA-10>APLOX1-1,qAR,EA4URC-13:!L:6pAMwiB& XLora Tracker/iGate
20260209174140EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate