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
20190217024726EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217030353EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217032017EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217033640EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217035303EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217040934EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217042557EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217044221EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217045843EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217051512EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217053137EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217054805EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217060432EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217062100EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217063723EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217065347EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217071012EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217072640EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217074307EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217075934EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217081601EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz
20190217083235EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA-Hotspot MMDVM 438.6000 MHz