APRS Packet Errors for VK3ARH (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
20180117011007VK3ARH>APZ013,qAS,VK3ARH-PL:; *170142z3648.91S14526.89E
20180117011501VK3ARH>APZ013,qAS,VK3ARH-PL:; *170152z3652.90S14516.10E
20180117014002VK3ARH>APZ013,qAS,VK3ARH-PL:; *170202z3654.44S14514.32E
20180117014007VK3ARH>APZ013,qAS,VK3ARH-PL:; *170212z3650.74S14518.84E
20180117020008VK3ARH>APZ013,qAS,VK3ARH-PL:; *170222z3650.77S14518.75E
20180117020013VK3ARH>APZ013,qAS,VK3ARH-PL:; *170232z3650.77S14518.75E
20180117044003VK3ARH>APZ013,qAS,VK3ARH-PL:; *170510z3650.80S14518.82E
20180117044502VK3ARH>APZ013,qAS,VK3ARH-PL:; *170519z3651.10S14518.81E
20180117050003VK3ARH>APZ013,qAS,VK3ARH-PL:; *170529z3651.10S14518.82E
20180117050502VK3ARH>APZ013,qAS,VK3ARH-PL:; *170538z3651.10S14518.82E
20180117051503VK3ARH>APZ013,qAS,VK3ARH-PL:; *170551z3651.11S14518.81E
20180117053003VK3ARH>APZ013,qAS,VK3ARH-PL:; *170601z3651.11S14518.82E
20180117054502VK3ARH>APZ013,qAS,VK3ARH-PL:; *170621z3650.73S14518.78E
20180117060003VK3ARH>APZ013,qAS,VK3ARH-PL:; *170611z3650.90S14518.70E
20180117060008VK3ARH>APZ013,qAS,VK3ARH-PL:; *170631z3650.76S14518.76E