APRS Packet Errors for EB7GQZ (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
20190618101139EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618102832EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618104519EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618110209EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618111855EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618113545EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618115232EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618120923EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618122610EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618124301EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618125945EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618131638EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618133333EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618135024EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618140712EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618142402EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618144050EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618145751EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618151440EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618153124EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190618154810EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz