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
20250702022145ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/020221z0.00000S/00.00000Ek290/000/A=000000 21C 1Mv 4.08V In 13.64V 0kmh
20250702022335ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/020223z0.00000S/00.00000Ek244/000/A=000000 21C 1Mv 4.05V In 13.64V 0kmh
20250702022639ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/020226z0.00000S/00.00000Ek343/000/A=000000 21C 1Mv 4.16V In 13.64V 0kmh
20250702071004ZS4BMX-10>APCLEY,TCPIP*,qAC,APRS-ZA:/020710z0.00000S/00.00000Ek258/000/A=000000 20C 1Mv 4.07V In 13.64V 0kmh