APRS Packet Errors for EA1DZR (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
20190217162930EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217164550EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217170212EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217171834EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217173459EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217175123EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217180744EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217182410EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217184034EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217185653EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217191313EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217192937EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217194559EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217200217EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217201838EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217203502EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217205129EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20190217210751EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz