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
20181214134453EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214140014EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214141534EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214143101EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214144621EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214150147EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214151712EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214153236EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214154759EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214160320EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214161841EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214163409EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214164934EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214170504EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214172042EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214173629EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214175151EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214180718EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214182244EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214183812EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214185336EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214190858EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz
20181214192424EB7GQZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB7GQZ-DP!3739.38N/-04-45.44rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8000 MHz