APRS Packet Errors for ZS4OIL-16 (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
20251115013606ZS4OIL-16>APCLEY,TCPIP*,qAC,APRS-ZA:/150136z0.00000S/00.00000Ev228/000/A=000000 28C 5St 4.16V If 12.40V 0kmh
20251115014907ZS4OIL-16>APCLEY,TCPIP*,qAC,APRS-ZA:/150149z0.00000S/00.00000Ev181/003/A=000000 29C 1Mv 4.22V If 12.40V 7kmh
20251115050915ZS4OIL-16>APCLEY,TCPIP*,qAC,APRS-ZA:/150509z2642.46S/0