APRS Packet Errors for EA1AYL (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
20210421024717EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421031820EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421034933EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421042203EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421045317EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421052604EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421055714EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421062658EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421070627EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz
20210421072415EA1AYL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!0000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 433.2500 MHz