APRS Packet Errors for EA4HBF (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
20181019175313EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019180841EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019182413EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019183949EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019185517EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019191052EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019192622EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019194150EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019195717EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019201251EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019202821EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019204348EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019205915EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019211443EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019213012EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019214538EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019220103EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019221628EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019223155EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019224719EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019230243EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019231816EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181019233343EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz