APRS Packet Errors for EB2EAU (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
20190624160639EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624162329EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624164023EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624165710EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624171405EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624173058EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624174754EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624180445EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624182137EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624183829EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624185525EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624191227EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624192916EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624194613EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624200305EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624201957EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624203646EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624205332EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624211025EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624212712EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190624214358EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz