APRS Packet Errors for MNORBS (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
20180921214214MNORBS>MNDMR,N0AGI-2,N0HOY-10*,WIDE2,qAR,N0TOR-10:;N0BVE-AIR*11111z4430N/031.MMPARPORT RPT 444.2MRC-ZONE 5 https://MNDMR.NET
20180921214237MNORBS>MNDMR,N0AGI-2,N0AGI-1,WIDE2*,qAR,N0TOR-10:;N0BVE-AIR*1111z4453.08N/09313.34WrNDR MSP-AIRPOTRT 44.95+ CC11 MRC-ON 5 htsMDR
20180922003439MNORBS>MNDMR,N0AGI-2,N0HOY-10*,WIDE2,qAR,N0TOR-10:;N0BVE-RDW*111111z4432.03N/023211WrMNMT42.7+CC2 R- ttp://MDRNT
20180922010934MNORBS>MNDMR,N0AGI-2,N0HOY-10*,WIDE2,qAR,N0TOR-10:;W0REA-WBL*111111z4503.67N/09301.rNMHIT ERLKP 4M-ONE ts:/N.T2
20180922022013MNORBS>MNDMR,N0AGI-2,N0AGI-1,WIDE2*,qAR,N0TOR-10:;N0AGI-BKH*111111z4443.39N/031.WB0A- *111z4423N/0931.4450H 100w/ymuionadWireX cces. wna ()o@K95=0816 https://aprsdroid.org/
20180922031712MNORBS>MNDMR,N0AGI-2,N0AGI-1,WIDE2*,qAR,N0TOR-10:;N0BVE-MSP*111111z4458.55N/031.rNMIEV IN4650+ CC2ZN ts:/MNME