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
20190420125751HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420131355HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420133007HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420134607HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420140204HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420141830HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420143515HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420150727HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420152331HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420153929HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420155525HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420161122HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420164321HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420165920HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420171524HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420173150HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420174747HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420180343HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420181940HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz
20190420185238HL1RR>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL1RR-DP!5000.00N/-0300.00ErRNG0034 IPSC2-KOREA MMDVM 439.9000@+5.0 MHz