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
20170423055102VK8GG>APZ013,qAS,VK8GG-PL:; *230629z3829.39S14515.92E
20170423060102VK8GG>APZ013,qAS,VK8GG-PL:; *230639z3831.08S14521.81E
20170423061101VK8GG>APZ013,qAS,VK8GG-PL:; *230649z3827.50S14528.78E
20170423062102VK8GG>APZ013,qAS,VK8GG-PL:; *230658z3820.82S14533.48E
20170423063102VK8GG>APZ013,qAS,VK8GG-PL:; *230708z3813.55S14530.56E
20170423064102VK8GG>APZ013,qAS,VK8GG-PL:; *230718z3809.77S14531.83E
20170423065102VK8GG>APZ013,qAS,VK8GG-PL:; *230729z3807.69S14533.70E
20170423070103VK8GG>APZ013,qAS,VK8GG-PL:; *230738z3807.69S14533.70E
20170423071103VK8GG>APZ013,qAS,VK8GG-PL:; *230748z3807.69S14533.70E