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
20181215170814EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20181215172332EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20181215173844EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20181215175356EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20181215180908EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20181215221241EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz
20181215224302EA1DZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1DZR-DP!4331.44N/-05-39.98rRNG0034 IPSC2-EA1Master MMDVM 432.0000 MHz