APRS Packet Errors for PI8NHN-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
20171218153355PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 7203442
20171218154626PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 4072443
20171218160227PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 5469312
20171218171511PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 6957860
20171218174607PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 0874893
20171218181703PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 7790125
20171218184759PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 9347701
20171218202239PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 2089640
20171218202803PI8NHN-10>PI4NHN,qAO,PI8RKW:;PQ: 6009013