APRS Packet Errors for ZS4BMX-9 (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
20260321085606ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/060000z0.00000S/00.00000Ev000/000/A=000000 22C 1Mv 4.10V If 12.75V 0kmh
20260321085953ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/210859z0.00000S/00.00000Ev000/000/A=000000 24C 5St 4.09V If 12.75V 0kmh
20260321090043ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/210900z0.00000S/00.00000Ev276/496/A=000000 24C 1Mv 4.08V If 12.73V 919kmh
20260321090110ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/210901z0.00000S/00.00000Ev229/169/A=000000 24C 1Mv 4.10V If 12.71V 314kmh
20260321090141ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/210901z0.00000S/00.00000Ev191/151/A=000000 24C 1Mv 4.09V If 12.71V 281kmh
20260321090212ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/210902z0.00000S/00.00000Ev131/281/A=000000 25C 1Mv 4.09V If 12.73V 522kmh
20260321090242ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/210902z0.00000S/00.00000Ev116/071/A=000000 25C 1Mv 4.10V If 12.73V 132kmh
20260321090742ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/210907z0.00000S/00.00000Ev000/000/A=000000 26C 5St 4.09V If 12.71V 0kmh
20260321101330ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/121013z0.00000S/00.00000Ev000/000/A=000000 25C 1Mv 4.12V If 12.62V 0kmh
20260321101718ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/211017z0.00000S/00.00000Ev000/000/A=000000 27C 5St 4.08V If 12.69V 0kmh