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
20181022190102EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022191644EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022193216EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022194751EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022200323EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022201855EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022203427EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022205001EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022210531EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022212101EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022213632EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022215205EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022220735EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022222305EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022223834EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022225405EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022230933EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022232509EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022234038EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181022235609EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181023001137EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181023002705EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181023004232EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz
20181023005803EA4HBF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4HBF-DP!4024.70N/-03-44.03rRNG0034 IPSC2-EA4Master MMDVM 430.5125 MHz