APRS Packet Errors for EA5GSD (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
20190620143514EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620145207EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620150908EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620152630EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620154328EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620160022EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620161727EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620163423EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620165127EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620170828EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620172524EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620174224EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620175917EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620181616EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620183318EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620185020EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620190950EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620192706EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190620194402EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz