APRS Packet Errors for EA5GIA (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
20190525090346EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525092134EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525093900EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525095627EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525101337EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525103051EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525104751EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525110503EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525112210EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525113913EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525115628EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525121338EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525123051EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525124748EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525130450EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525132157EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525133859EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525135555EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525141305EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190525143001EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz