APRS Packet Errors for ZS2JO-10 (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
20250711204801ZS2JO-10>APCLEY,TCPIP*,qAC,APRS-ZA:/112048z0000.00N/00000.00E>000/000/A=000000 27C 5St 4.16V If 12.46V 0kmh
20250711205305ZS2JO-10>APCLEY,TCPIP*,qAC,APRS-ZA:/112048z0000.00N/00000.00E>000/000/GPS Poor
20250711205802ZS2JO-10>APCLEY,TCPIP*,qAC,APRS-ZA:/112048z0000.00N/00000.00E>000/000/GPS Poor
20250711210302ZS2JO-10>APCLEY,TCPIP*,qAC,APRS-ZA:/112048z0000.00N/00000.00E>000/000/GPS Poor
20250711210802ZS2JO-10>APCLEY,TCPIP*,qAC,APRS-ZA:/112048z0000.00N/00000.00E>000/000/GPS Poor
20250711211302ZS2JO-10>APCLEY,TCPIP*,qAC,APRS-ZA:/112048z0000.00N/00000.00E>000/000/GPS Poor
20250711211802ZS2JO-10>APCLEY,TCPIP*,qAC,APRS-ZA:/112048z0000.00N/00000.00E>000/000/GPS Poor