APRS Packet Errors for G4KWT (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
20191114182831G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114192753G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114195733G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114202714G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114205655G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114212636G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114215617G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114222557G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114225539G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114232520G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker
20191114235502G4KWT>APAGW,qAR,G0JMS:=0.0/0.0 AGWtracker