APRS Packet Errors for N0NEB-2 (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
20210302140533N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302143549N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302150532N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302153902N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302160533N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302163858N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302170532N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302173634N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302180532N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302183532N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302190532N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20210302193534N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI