APRS Packet Errors for HL1RR (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
20190120154316HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120155913HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120161510HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120163112HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120164716HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120170320HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120171917HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120173513HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120175118HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120180716HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120182312HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120183942HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120185621HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120191229HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120192830HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120194426HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120200029HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120201632HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120203228HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120204826HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120210430HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190120212026HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz