APRS Packet Errors for EB5AG (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
20210115175015EB5AG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5AG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 439.9750 MHz
20210115182045EB5AG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5AG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 439.9750 MHz
20210115185117EB5AG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5AG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 439.9750 MHz
20210115192152EB5AG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5AG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 439.9750 MHz
20210115195220EB5AG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5AG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 439.9750 MHz
20210115202253EB5AG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5AG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 439.9750 MHz
20210115205331EB5AG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5AG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 439.9750 MHz
20210115212356EB5AG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5AG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 439.9750 MHz