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
20190421164627EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421170306EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421172001EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421173648EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421175331EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421181013EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421182659EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421184402EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421190045EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421191728EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421193419EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421195102EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421200743EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421202420EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421204108EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421205755EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421211436EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421213122EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20190421214759EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz