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
20171215154543OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-2,T2CZECH:!4939.48N/0249.09E_000/000g000t027r000P000L005h00b09856wATM Brdy
20171215165648OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-2,T2CZECH:!4Y39.48N/01349.09E_000/000g000t029r000P000L015h00b09859wATM Brdy
20171215174233OK5TVR-4>APRS,DB0HHB,WIDE1*,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/013
20171215181301OK5TVR-4>APRS,DB0HHB,WIDE1*,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.09E
20171215212558OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-2,T2CZECH:!4939.48N/0134909E_225/000g000t028r000P000L019h00b09859wATM Brdy