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
20180121230507VK3ARH>APZ013,qAS,VK3ARH-PL:; *212339z3648.32S14520.84E
20180121232502VK3ARH>APZ013,qAS,VK3ARH-PL:; *212346z3641.94S14519.22E
20180121232507VK3ARH>APZ013,qAS,VK3ARH-PL:; *212356z3636.75S14519.14E
20180121233003VK3ARH>APZ013,qAS,VK3ARH-PL:; *220005z3633.41S14521.13E
20180121234002VK3ARH>APZ013,qAS,VK3ARH-PL:; *220015z3625.57S14523.38E
20180121235002VK3ARH>APZ013,qAS,VK3ARH-PL:; *220025z3623.03S14523.22E
20180122000003VK3ARH>APZ013,qAS,VK3ARH-PL:; *220035z3623.21S14525.61E
20180122001007VK3ARH>APZ013,qAS,VK3ARH-PL:; *220045z3623.23S14525.57E
20180122002502VK3ARH>APZ013,qAS,VK3ARH-PL:; *220055z3623.23S14525.56E