APRS Packet Errors for KE5ISM-3 (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
20180218194435KE5ISM-3>APOTW1,N5LUY-2,WIDE2*,qAR,N5KWD-10:!3046.23N/0961.03W_22/hO1
20180218205050KE5ISM-3>APOTW1,N5LUY-2,WIDE2*,qAR,N5KWD-10:!3046.23N/09617.03W_15/t0h01O1
20180218211013KE5ISM-3>APOTW1,N5LUY-2,WIDE2*,qAR,N5KWD-10:!3046.23N/09617.03W_045/g011t07800h1V1OW
20180218215038KE5ISM-3>APOTW1,N5LUY-2,WIDE2*,qAR,N5KWD-10:!03W_57003g07078P00h73b10166V123TW
20180218235725KE5ISM-3>APOTW1,N5LUY-2,WIDE2*,qAR,N5KWD-10:!3046.23N/09617.0iis wyyq@gmil.com
20180219001219KE5ISM-3>APOTW1,N5LUY-2,WIDE2*,qAR,N5KWD-10:!3046.236.0/g0072P0076b10154V123TW