APRS Packet Errors for OZ1IDG (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
20190422171357OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422173048OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422174738OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422180415OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422182110OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422183752OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422185454OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422191134OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422192822OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422194504OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422200205OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422201859OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422203552OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422205239OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422210926OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422212606OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422214248OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422215929OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422221611OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422223257OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20190422224938OZ1IDG>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1IDG-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DK MMDVM 434.5000 MHz