APRS Packet Errors for ZS4BMX-9 (last 24 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
20260731103158ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/111031z0.00000S/00.00000Ev000/000/A=000000 31C 1Mv 4.13V In 14.31V 0kmh
20260731103258ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/311032z0.00000S/00.00000Ev206/010/A=000000 32C 1Mv 4.09V In 14.30V 19kmh
20260731112020ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/311120z0.00000S/00.00000Ev000/000/A=000000 24C 1Mv 4.10V In 14.01V 0kmh
20260731112132ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/311121z0.00000S/00.00000Ev098/028/A=000000 24C 1Mv 4.08V In 14.12V 52kmh
20260731155052ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/311550z0.00000S/00.00000Ev000/000/A=000000 21C 1Mv 4.14V In 13.73V 0kmh
20260801043540ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/060000z0.00000S/00.00000Ev000/000/A=000000 7C 1Mv 4.13V If 12.55V 0kmh
20260801055207ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/120552z0.00000S/00.00000Ev000/000/A=000000 9.C 1Mv 4.13V If 12.00V 0kmh
20260801071204ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/010712z0.00000S/00.00000Ev005/000/A=000000 19C 1Mv 4.10V If 12.68V 0kmh