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
20260306094755ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/110947z0.00000S/00.00000Ev000/000/A=000000 26C 1Mv 4.17V In 14.03V 0kmh
20260306105937ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/061059z0.00000S/00.00000Ev260/004/A=000000 30C 1Mv 4.08V In 13.99V 8kmh
20260306153439ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/061534z0.00000S/00.00000Ev000/000/A=000000 21C 1Mv 4.09V In 14.24V 0kmh
20260306184209ZS4BMX-9>APCLEY,TCPIP*,qAC,APRS-ZA:/111842z0.00000S/00.00000Ev000/000/A=000000 19C 1Mv 4.08V In 13.92V 0kmh