APRS Packet Errors for EA4GSB-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
20260208151413EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.25V
20260208154413EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.24V
20260208161414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.29V
20260208164414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.26V
20260208171414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.27V
20260208174414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.25V
20260208181414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.23V
20260208184414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.23V
20260208191414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.23V
20260208194414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.21V
20260208201415EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.19V
20260208204414EA4GSB-10>APLRG1,TCPIP*,qAC,T2CHILE:!L:)IJMV3Fa GLoRa APRS IGATE juankar VK Batt=4.14V