APRS Packet Errors for EA7ERD (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
20190220074226EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220075855EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220081524EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220083202EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220084839EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220090509EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220092137EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220093805EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220095439EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220101107EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220102739EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220104405EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220110031EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220111658EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220113332EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220115008EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220120648EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220122321EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220123956EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220125625EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220131254EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190220132925EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz