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
20180319074503VK3ARH>APZ013,qAS,VK3ARH-PL:; *190821z3649.04S14512.76E
20180319080003VK3ARH>APZ013,qAS,VK3ARH-PL:; *190831z3647.27S14509.12E
20180319081003VK3ARH>APZ013,qAS,VK3ARH-PL:; *190840z3649.04S14508.80E
20180319082503VK3ARH>APZ013,qAS,VK3ARH-PL:; *190900z3650.76S14518.72E
20180319084004VK3ARH>APZ013,qAS,VK3ARH-PL:; *190851z3649.54S14518.63E
20180319084009VK3ARH>APZ013,qAS,VK3ARH-PL:; *190911z3650.76S14518.72E
20180319084503VK3ARH>APZ013,qAS,VK3ARH-PL:; *190920z3650.76S14518.72E
20180319090008VK3ARH>APZ013,qAS,VK3ARH-PL:; *190930z3650.76S14518.72E
20180319091001VK3ARH>APZ013,qAS,VK3ARH-PL:; *190940z3650.76S14518.72E
20180319091502VK3ARH>APZ013,qAS,VK3ARH-PL:; *190950z3650.76S14518.72E