APRS Packet Errors for VK8GG (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
20170623035102VK8GG>APZ013,qAS,VK8GG-PL:; *230428z3804.96S14529.27E
20170623040103VK8GG>APZ013,qAS,VK8GG-PL:; *230438z3804.96S14529.28E
20170623041103VK8GG>APZ013,qAS,VK8GG-PL:; *230447z3804.95S14529.26E
20170623043103VK8GG>APZ013,qAS,VK8GG-PL:; *230457z3804.96S14529.28E
20170623043109VK8GG>APZ013,qAS,VK8GG-PL:; *230507z3807.68S14533.62E
20170623044102VK8GG>APZ013,qAS,VK8GG-PL:; *230518z3807.69S14533.69E
20170623051102VK8GG>APZ013,qAS,VK8GG-PL:; *230527z3807.69S14533.66E
20170623051108VK8GG>APZ013,qAS,VK8GG-PL:; *230537z3803.94S14530.68E
20170623051114VK8GG>APZ013,qAS,VK8GG-PL:; *230547z3800.38S14530.85E