APRS Packet Errors for OK9TVR-10 (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
20190216153313OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys
20190216161256OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys
20190216165228OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys
20190216173157OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys
20190216181123OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys
20190216185048OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys
20190216193011OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys
20190216200933OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys
20190216204854OK9TVR-10>APZM4A,TCPIP*,qAC,T2CZECH:)DV001 _4947.00N/01317.19EQMonitoring dolni vlkys