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
20171218013003VK3ARH>APZ013,qAS,VK3ARH-PL:; *180206z3646.74S14509.09E
20171218014503VK3ARH>APZ013,qAS,VK3ARH-PL:; *180216z3647.03S14509.29E
20171218015007VK3ARH>APZ013,qAS,VK3ARH-PL:; *180226z3647.03S14509.27E
20171218020502VK3ARH>APZ013,qAS,VK3ARH-PL:; *180236z3646.99S14509.25E
20171218024002VK3ARH>APZ013,qAS,VK3ARH-PL:; *180304z3650.76S14518.74E
20171218024007VK3ARH>APZ013,qAS,VK3ARH-PL:; *180314z3650.76S14518.72E
20171218025002VK3ARH>APZ013,qAS,VK3ARH-PL:; *180324z3650.76S14518.75E