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
20190818194954EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818200643EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818202329EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818204013EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818205656EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818211346EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818213038EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818214724EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818220407EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818222056EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818223739EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818225428EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818231113EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818232759EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190818234443EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190819000132EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190819001815EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190819003502EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190819005146EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190819010830EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz
20190819012514EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 434.5500 MHz