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
20190326191228EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326192938EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326194632EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326200324EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326202027EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326203738EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326205424EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326211112EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326212759EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326214442EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326220120EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326221804EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326223452EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326225136EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326230816EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326232456EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326234135EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190326235815EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz