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
20190216192839EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216192840EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216194517EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216194517EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216200155EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216200155EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216201841EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216201841EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216203527EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216203527EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216205212EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216205212EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216210853EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216210853EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216212512EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216212512EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216214133EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216214133EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216215840EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216215840EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216221502EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216221502EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216223126EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216223126EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz
20190216224743EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3832.39N/000-30.33rRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190216224743EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3831.25N/000-32.50rRNG0034 IPSC2-EA4Master MMDVM 144.9625 MHz