APRS Packet Errors for G0VEA (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
20181018184857G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *181848z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018190357G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *181903z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018191857G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *181918z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018193357G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *181933z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018194857G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *181948z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018200357G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *182003z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018201857G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *182018z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018203357G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *182033z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018204857G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *182048z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018210357G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *182103z5037.41N/-0323.84ErDVRPTR V2 Exmouth
20181018211857G0VEA>APZCCS,TCPIP*,qAU,CCS002:;G0VEA-B *182118z5037.41N/-0323.84ErDVRPTR V2 Exmouth