APRS Packet Errors for EA2AFF-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
20260208163732EA2AFF-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9JMPN9y3& XLora Tracker/iGate
20260208170736EA2AFF-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9JMPN9y3& XLora Tracker/iGate
20260208173746EA2AFF-10>APLOX1,TCPIP*,qAC,T2FINLAND:!L9JMPN9y3& XLora Tracker/iGate
20260208180750EA2AFF-10>APLOX1,WIDE1-1,Q06L5,qAR,EA2AIV-10:!L9JMPN9y3& XLora Tracker/iGate
20260208183754EA2AFF-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L9JMPN9y3& XLora Tracker/iGate
20260208190757EA2AFF-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L9JMPN9y3& XLora Tracker/iGate
20260208193801EA2AFF-10>APLOX1,TCPIP*,qAC,T2SPAIN:!L9JMPN9y3& XLora Tracker/iGate
20260208200806EA2AFF-10>APLOX1,TCPIP*,qAC,T2CZECH:!L9JMPN9y3& XLora Tracker/iGate
20260208203812EA2AFF-10>APLOX1,TCPIP*,qAC,T2FINLAND:!L9JMPN9y3& XLora Tracker/iGate
20260208210824EA2AFF-10>APLOX1,WIDE1-1,Q02L3,qAR,EA2AIV-10:!L9JMPN9y3& XLora Tracker/iGate
20260208213833EA2AFF-10>APLOX1,WIDE1-1,Q06L5,qAR,EA2AIV-10:!L9JMPN9y3& XLora Tracker/iGate
20260208220837EA2AFF-10>APLOX1,WIDE1-1,qAR,EA2DRO-10:!L9JMPN9y3& XLora Tracker/iGate