APRS Packet Errors for N7BYU-1 (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
20180423034731N7BYU-1>APN391,HOLDEN*,WIDE2-1,qAR,ABAJO:!4014.91N11138.83W#PHG8330
20180423041730N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423044730N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423051730N7BYU-1>APN391,KF6RAL-2,WIDE2*,qAR,KB7STN-3:!4014.91N11138.83W#PHG8330
20180423054730N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423061730N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423064730N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423071730N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423074729N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423081729N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423084730N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180423091729N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330