APRS Packet Errors for EA4AES (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
20190418101536EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418103224EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418104913EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418110610EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418112317EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418114029EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418115721EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418121414EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418123109EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418124805EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418130455EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418132146EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418133833EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418135517EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418141157EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418142844EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418144546EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz
20190418150240EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.69N/-03-11.90rRNG0034 IPSC2-EA-Hotspot MMDVM 434.9500 MHz