APRS Packet Errors for HL3BAT (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
20190218173154HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218174824HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218180500HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218182149HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218183845HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218185543HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218191229HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218192919HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218194559HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218200241HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218201921HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218203608HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218205249HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218210935HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218212618HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218214314HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218215958HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218221639HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218223321HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218225025HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218230707HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190218232347HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2POLC:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz