APRS Packet Errors for W2LV-3 (last 24 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
20180617025343W2LV-3>GPS,qAR,W3OI:!4111.54NS07445
20180617043456W2LV-3>GPS,qAR,W3OI:;147.300NJ*1d@@@c)Inspira!3950.62N/07509.01WhPHG35
20180617125305W2LV-3>BEACON,qAR,W3OI:;147.300NJ*111111z4111.Yaesu FTM-400DR_%
20180617131241W2LV-3>APN383,WIDE2-1,qAR,W3OI:!4111.54Nex NJ
20180617140510W2LV-3>GPS,qAR,W3OI:;147.300NJ*111111z4111.54N/07445.2
20180617151306W2LV-3>BEACON,qAR,W3OI:;147.300NJ*111111z4111.
20180617152458W2LV-3>GPS,qAR,W3OI:;147.300NJ*111111z4111.
20180617153443W2LV-3>GPS,qAR,W3OI:;147.300NJ*1111ng System {UIV32N}
20180617174340W2LV-3>GPS,qAR,W3OI:!4111.54NS07445
20180617184502W2LV-3>GPS,qAR,W3OI:;147.300NJ*111111z4111.54N/0744P RADIO_%
20180617194343W2LV-3>GPS,qAR,W3OI:!4111.54NS07445
20180617221303W2LV-3>BEACON,qAR,W3OI:;147.300NJ*111111z4111.54N/0
20180617224326W2LV-3>BEACON,qAR,W3OI:;147.300NJ*1111`STARSHIP RADIO_%