APRS Packet Errors for EA4EUM (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
20260208152029EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.26V
20260208155029EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.19V
20260208162029EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.25V
20260208165029EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.23V
20260208172029EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.21V
20260208175030EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.27V
20260208182030EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.27V
20260208185030EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.23V
20260208192030EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.25V
20260208195030EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.21V
20260208202030EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.25V
20260208205030EA4EUM>APLRG1,TCPIP*,qAC,T2SYDNEY:!L:W,"MvK1a GAPRS LoRa Batt=4.20V