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
20170326050102VK8GG>APZ013,qAS,VK8GG-PL:; *260531z4319.21S14714.56E
20170326051101VK8GG>APZ013,qAS,VK8GG-PL:; *260540z4318.84S14714.58E
20170326052102VK8GG>APZ013,qAS,VK8GG-PL:; *260550z4318.29S14714.80E
20170326053102VK8GG>APZ013,qAS,VK8GG-PL:; *260600z4317.95S14715.60E
20170326054102VK8GG>APZ013,qAS,VK8GG-PL:; *260610z4318.74S14716.65E
20170326054108VK8GG>APZ013,qAS,VK8GG-PL:; *260620z4317.43S14719.67E
20170326060102VK8GG>APZ013,qAS,VK8GG-PL:; *260630z4317.44S14719.68E
20170326060108VK8GG>APZ013,qAS,VK8GG-PL:; *260640z4317.44S14719.69E
20170326061102VK8GG>APZ013,qAS,VK8GG-PL:; *260650z4317.43S14719.68E
20170326063102VK8GG>APZ013,qAS,VK8GG-PL:; *260700z4317.44S14719.67E
20170326064102VK8GG>APZ013,qAS,VK8GG-PL:; *260710z4317.43S14719.69E
20170326064108VK8GG>APZ013,qAS,VK8GG-PL:; *260719z4317.44S14719.67E
20170326070103VK8GG>APZ013,qAS,VK8GG-PL:; *260730z4317.43S14719.68E
20170326070108VK8GG>APZ013,qAS,VK8GG-PL:; *260739z4317.43S14719.68E