APRS Packet Errors for PI8HLM-10 (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
20171020080948PI8HLM-10>PA1VW,qAO,PI8RKW:;PQ: 1953274
20171020081148PI8HLM-10>PA1VW,qAO,PI8RKW:;PQ: 8463986
20171020081234PI8HLM-10>PA1VW,qAO,PI8RKW:;PQ: 9878898
20171020081320PI8HLM-10>PA1VW,qAO,PI8RKW:;PQ: 3062348
20171020081358PI8HLM-10>PA1VW,qAO,PI8RKW:;PQ: 5435231
20171020081445PI8HLM-10>PA1VW,qAO,PI8RKW:;PQ: 2419983
20171020081921PI8HLM-10>PA1VW,qAO,PI8RKW:;PQ: 8133768
20171020083130PI8HLM-10>PI4NHN,qAO,PI8RKW:;PQ: 2056443
20171020083226PI8HLM-10>PI4NHN,qAO,PI8RKW:=ӾZyEmEU(NݻIΜp{魄=KȗޮYQ>xiAncK]]w6TD<-~!n VDz3iJt8l8=kNC&zpy^{
20171020083713PI8HLM-10>PI4NHN,qAO,PI8RKW:;PQ: 2004032
20171020084221PI8HLM-10>PI4NHN,qAO,PI8RKW:;PQ: 3247389
20171020093507PI8HLM-10>PA3GON,qAO,PI8RKW:;PQ: 5466242
20171020093912PI8HLM-10>PA3GON,qAO,PI8RKW:;PQ: 0201851