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
20190616091245EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616092936EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616094629EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616100326EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616102015EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616103718EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616105423EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616111127EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616112828EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616114522EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616120219EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616121921EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616123629EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616125327EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616131022EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616132722EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616134424EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616140120EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616141819EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616143520EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz
20190616145217EB2EAU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB2EAU-DP!4030.14N/-03-31.31rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8125@-9.4 MHz