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
20171016195624OK5TVR-4>APRS,OK0BAD-2*,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.09E_000/00(g000t056r000P000L060h00b10
20171016203632OK5TVR-4>APRS,OK1CMJ-2*,WIDE2-2,qAR,OK5TVR-2,T2CZECH:!4939.48N/01349.09E_09
20171016211640OK5TVR-4>APQS,WIBE1-1,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.09E_00300
20171016234714OK5TVR-4>APRS,OK1OQH-2,OK0BAD-2*,WIDC2-1,qAR,OK5TVR-1,T2CZECH:!4939.48N/0249.09E_315/000g000t057r000P000L011h00b10116wATM Bqdy
20171017003724OK5TVR-4>APRS,OK1CMJ-2,OK0BAD-2*,WIDE2-1,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.09E_315/0(0g000t055r000P000L005h00b10116wATM Brdy
20171017010228OK5TVR-4>GPRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-2:!4939.48N/0134909E_000/000k000t057r10PP00L00400b10716wATMBrdy