APRS Packet Errors for EA2ADP-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
20260208162544EA2ADP-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9HSnN9/X& XLora Tracker/iGate P=4.23V
20260208164048EA2ADP-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9HSnN9/X& XLora Tracker/iGate P=4.23V
20260208165557EA2ADP-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9HSnN9/X& XLora Tracker/iGate P=4.43V
20260208171101EA2ADP-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9HSnN9/X& XLora Tracker/iGate P=4.35V
20260208172605EA2ADP-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9HSnN9/X& XLora Tracker/iGate P=4.26V
20260208174115EA2ADP-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9HSnN9/X& XLora Tracker/iGate P=4.28V
20260208175623EA2ADP-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9HSnN9/X& XLora Tracker/iGate P=4.42V
20260208181128EA2ADP-10>APLOX1,TCPIP*,qAC,T2UKRAINE:!L9HSnN9/X& XLora Tracker/iGate P=4.43V
20260208182357EA2ADP-10>APLOX1,TCPIP*,qAC,T2ROMANIA:!L9HSnN9/X& XLora Tracker/iGate P=4.39V
20260208183904EA2ADP-10>APLOX1,TCPIP*,qAC,T2ROMANIA:!L9HSnN9/X& XLora Tracker/iGate P=4.21V