APRS Packet Errors for HL1CCD (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
20190918143439HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918145017HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918150546HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918152114HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918153642HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918155220HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918160749HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918162317HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918163845HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918165423HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918170953HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918172519HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918174050HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918175642HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918181209HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918182747HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918184320HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918185855HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918191426HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918192955HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918194524HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918200104HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20190918201631HL1CCD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1CCD-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz