APRS Packet Errors for N0AGI-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
20180925133812N0AGI-1>APMI06,qAR,N0TOR-10:;N0AGI-BKH*251337/4443.39/032WB L BUNVLLE DMR 3+NACMJ
20180925142257N0AGI-1>APMI06,qAR,N0TOR-10:=4503.11NJ0934.2WARS WIDE Digi+iGa tpNG.com . John3:6```@a!4409.98N573i racy M H
20180925153811N0AGI-1>APMI06,qAR,N0TOR-10:;N0AGI-BKH*251538/443RVLLE M 4.NACMJ .6
20180925162239N0AGI-1>APMI06,qAR,N0TOR-10:;N0AGI-FBL*251622/417.96/03WARIBAULT DMR PT4.7tA.COM . John 316q
20180925165307N0AGI-1>APMI06,qAR,N0TOR-10:;N0AGI-BKH*251653/4443.39N0917.2WBNIDRRPT 443.125+ N0AGI.COM John 3.16