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
20201027031916N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027034914N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027041913N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027044914N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027051914N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027054914N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027061920N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027071914N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027074915N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027081921N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI
20201027084914N0NEB-2>APN391,WIDE2-2,qAR,KC0OZ-10:;4149.48N/10325.06W SCOTTSBLUFF DIGI