APRS Packet Errors for ZS4BMX-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
20250802082306ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/020823z0.00000S/00.00000Ek267/000/A=000000 17C 1Mv 4.06V In 13.49V 0kmh
20250802085100ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/020850z0.00000S/00.00000Ek275/000/A=000000 18C 1Mv 4.08V In 13.49V 0kmh
20250802091048ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/020910z0.00000S/00.00000Ek325/000/A=000000 18C 1Mv 4.10V In 13.49V 0kmh
20250802091435ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/020914z0.00000S/00.00000Ek066/000/A=000000 18C 1Mv 4.07V In 13.49V 0kmh
20250802100614ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/021006z0.00000S/00.00000Ek148/000/A=000000 19C 1Mv 4.05V In 13.49V 0kmh
20250802102049ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/021020z0.00000S/00.00000Ek036/000/A=000000 19C 1Mv 4.10V In 13.48V 0kmh
20250802114038ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/021140z0.00000S/00.00000Ek339/001/A=000000 20C 1Mv 4.16V In 13.49V 0kmh