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
20170819161418OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349
20170819162922OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.09ddj^```````jrP```````f``b``hp@
20170819171934OK5TVR-4>APRS,DB0HHB,WIDE1*,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/0134919E_270/000g000t058r000P000L002h00b10044wATM Brdy
20170819184953OK5TVR-4>APRS,DB0HHB,WIDE1*,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.0D_<45/006g<00t054r006P000L000h00b10051wATM Brdy
20170819195506OK5TVR-4>APRS,WIDE1-1,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.0 E_270/000g000t052r000P000L009h00b10059wATM Brdy
20170819203516OK5TVR-4>APRS,OK0BAD-2*,WIDE2-2,qAR,OK5TVR-1,T2CZECH:!4939.48N/01349.09E_000/(00g000t051r000P000L004h00b10059wATM Brdy