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
20190124082845EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124084508EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124090121EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124091742EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124093404EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124095023EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124100642EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124102251EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124103942EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124105609EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124111248EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124112859EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124114520EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124120128EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124121740EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124123355EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124125021EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124130641EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124132300EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz
20190124133913EA5GIA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GIA-DP!3926.20N/000-22.60rRNG0034 IPSC2-EA4Master MMDVM 432.9000 MHz