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
20181019132939EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019134508EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019140036EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019141607EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019143134EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019144702EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019150230EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019151800EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019153329EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019154857EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019160426EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019161956EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019163532EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019165101EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019170630EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019172217EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019173745EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019175313EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019180841EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019182413EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019183949EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019185517EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181019191052EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz