APRS Packet Errors for EA4CZ-4 (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
20260209092919EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.15V
20260209095919EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.09V
20260209103120EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.08V
20260209105920EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.20V
20260209112920EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=3.96V
20260209115920EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.28V
20260209123120EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.04V
20260209125920EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.14V
20260209132921EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.17V
20260209135921EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.10V
20260209143121EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.07V
20260209145921EA4CZ-4>APLOX1,TCPIP*,qAC,T2CZECH:!L:VN5M-*!a XLoRa iGate by Daniboy P=4.05V