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
20181017052430EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017053954EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017055521EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017061045EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017062609EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017064136EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017065705EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017071232EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017072757EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017074323EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017075852EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017081419EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017082946EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017084514EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017090044EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017091612EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017093141EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017094709EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017100248EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017101817EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017103345EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017104913EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017110444EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz
20181017112013EA7ERD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7ERD-DP!3646.56N/-02-48.57rRNG0034 IPSC2-EA4Master MMDVM 438.6000 MHz