APRS Packet Errors for OK5TVR-4 (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
20171017203637OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-2,T2CZECH:!493Y.48N/01349.09E_135/000g000t055r000P000L020h00b20059wATM Brdy
20171017204142OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-2,T2CZECH:!4:39.48N/01349.09E_180/000g000t054r000P000L005h00b10059wATM Brdy
20171017212225OK5TVR-4>APRS,OK1CMJ-2,OK0BAD-2*,WIDE2-1,qAR,OK5TVR-1,T2CZECH:!4939.48M/01349.09E_135/000g000t052r000P000L004h00b10055wATM Brdy
20171017234432OK5TVR-4>APRS,OIDE1-1,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.09E_090/61g000t052r000P000L022h00b10048wATM Brdy
20171017234937OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.4/3:9(&4 &!9
20171018001000OK5TVR-4>APRS,SR6NPK,WIDE1,OK0BAD-2*,WIDE2-1,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.09E_04.000g01t054r000P000L000h00b10044wATM Brdy