APRS Packet Errors for EA5AYB (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
20190618011244EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618012925EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618014604EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618020242EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618021918EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618023559EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618025235EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618030912EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618032549EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618034228EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618035905EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618041542EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618043220EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618044901EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618050542EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618052222EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618053901EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618055542EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618061221EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618062903EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618064544EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618070230EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz