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
20190618100524EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618102204EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618103846EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618105528EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618111214EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618112854EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618114533EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618120213EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618121853EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618123534EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618125215EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618130856EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618132535EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618134218EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618135856EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618141535EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618143217EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618144858EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618150536EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618152218EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190618153901EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz