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
20190917012357HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917014013HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917015539HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917021107HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917022632HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917024208HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917025734HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917031259HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917032824HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917034356HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917035921HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917041447HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917043014HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917044548HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917050113HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917051640HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917053205HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917054738HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917060304HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917061830HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917063355HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917064928HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz
20190917070455HL3BAT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL3BAT-DP!12722.50N/03621.25rRNG0034 IPSC2-KOREA MMDVM 438.3000@-7.0 MHz