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
20260208133333EA4XA-10>APLOX1-1,qAR,EA4URC-13:!L:6pAMwiB& XLora Tracker/iGate
20260208133532EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208140337EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208143340EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208150350EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208153355EA4XA-10>APLOX1-1,qAR,EA4URC-13:!L:6pAMwiB& XLora Tracker/iGate
20260208153555EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208160401EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208163410EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208170414EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208173424EA4XA-10>APLOX1-1,qAR,EA4URC-13:!L:6pAMwiB& XLora Tracker/iGate
20260208173624EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208180430EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208183439EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate
20260208190448EA4XA-10>APLOX1-1,TCPIP*,qAC,T2DENMARK:!L:6pAMwiB& XLora Tracker/iGate