APRS Packet Errors for ZS6EY-17 (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
20260616052627ZS6EY-17>APCLEY,TCPIP*,qAC,APRS-ZA:/160526z16 Jun S/02749.87Ev000/001/A=004801 39C 1Mv 4.17V If 12.23V 3kmh GP1
20260616053908ZS6EY-17>APCLEY,TCPIP*,qAC,APRS-ZA:/160539z16 Jun S/02749.87Ev000/000/A=004821 48C 1Mv 4.15V If 12.06V 7kmh GP1
20260616131902ZS6EY-17>APCLEY,TCPIP*,qAC,APRS-ZA:/161319z16 Jun S/02749.87Ev000/000/A=004740 50C 1Mv 4.13V If 12.13V 1kmh GP1
20260616133302ZS6EY-17>APCLEY,TCPIP*,qAC,APRS-ZA:/161333z16 Jun S/02749.87Ev000/001/A=004769 50C 1Mv 4.17V If 12.12V 1kmh GP1
20260616135646ZS6EY-17>APCLEY,TCPIP*,qAC,APRS-ZA:/161356z16 Jun S/02749.88Ev000/002/A=004870 40C 1Mv 4.18V If 12.19V 5kmh GP1
20260616180946ZS6EY-17>APCLEY,TCPIP*,qAC,APRS-ZA:/161809z16 Jun S/02749.89Ev000/000/A=004847 40C 1Mv 4.18V If 12.17V 3kmh GP1
20260616195606ZS6EY-17>APCLEY,TCPIP*,qAC,APRS-ZA:/161956z16 Jun S/02749.88Ev000/000/A=004808 50C 1Mv 4.17V If 12.08V 1kmh GP1
20260616231318ZS6EY-17>APCLEY,TCPIP*,qAC,APRS-ZA:/162313z16 Jun S/02749.87Ev000/000/A=004788 42C 5St 4.18V If 12.15V 3kmh GP1