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
20180419204740N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180419211740N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180419214739N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180419221740N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180419224739N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180419231739N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180419234739N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180420001739N7BYU-1>APN391,KF6RAL-1,WIDE2*,qAO,WEBER:!4014.91N11138.83W#PHG8330
20180420003414N7BYU-1>BEACON,qAR,KB7STN-3:;145.33-a*4014.91N11138.83WrT100 Net 9PM Th BYUARC
20180420004740N7BYU-1>APN391,KF6RAL-1*,WIDE2-1,qAR,KB7STN-3:!4014.91N11138.83W#PHG8330
20180420010739N7BYU-1>APN391,qAR,KB7STN-3:!4014.91N11138.83W#PHG8330
20180420011740N7BYU-1>APN391,HOLDEN,WIDE2*,qAR,ABAJO:!4014.91N11138.83W#PHG8330
20180420014739N7BYU-1>APN391,KF6RAL-2*,WIDE2-1,qAR,KB7STN-3:!4014.91N11138.83W#PHG8330
20180420021739N7BYU-1>APN391,KF6RAL-2,WIDE2*,qAR,KB7STN-3:!4014.91N11138.83W#PHG8330
20180420023414N7BYU-1>BEACON,qAR,KB7STN-3:;145.33-a*4014.91N11138.83WrT100 Net 9PM Th BYUARC