APRS Packet Errors for AI4UE (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
20191118134506AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118140030AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118141554AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118143120AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118144644AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118150208AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118151733AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118153301AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118154826AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118160352AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118161920AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118163449AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118165015AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118170541AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118172106AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118173636AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118175204AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118180730AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118182256AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118183826AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118185356AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118190922AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz
20191118192448AI4UE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)AI4UE-DP!3706.18N/-79-23.07rRNG0034 IPSC2-DL-HOTSPOT MMDVM 444.3500 MHz