APRS Packet Errors for EA4GRR (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
20190222010159EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222011833EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222013507EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222015138EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222020810EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222022456EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222024141EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222025819EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222031450EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222033124EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222034759EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222040430EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222042100EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222043731EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222045405EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222051036EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222052706EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222054337EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222060012EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222061645EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222063316EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
20190222064952EA4GRR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GRR-DP!3928.07N/-06-22.72rRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz