APRS Packet Errors for ZS4OIL-18 (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
20261113044135ZS4OIL-18>APCLEY,TCPIP*,qAC,APRS-ZA:/130441z0.00000S/00.00000Ev266/006/A=000000 32C 1Mv 4.04V In 13.99V 20kmh
20261113044453ZS4OIL-18>APCLEY,TCPIP*,qAC,APRS-ZA:/130444z0.00000S/00.00000Ev254/002/A=000000 32C 1Mv 4.04V In 13.99V 3kmh
20261113044514ZS4OIL-18>APCLEY,TCPIP*,qAC,APRS-ZA:/130445z0.00000S/00.00000Ev272/000/A=000000 32C 1Mv 4.03V In 13.99V 4kmh
20261113044535ZS4OIL-18>APCLEY,TCPIP*,qAC,APRS-ZA:/130445z0.00000S/00.00000Ev038/002/A=000000 32C 1Mv 4.04V In 14.01V 3kmh