APRS Packet Errors for EA4RMS (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
20190216192839EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216194517EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216200155EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216201841EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216203527EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216205212EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216210853EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216212512EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216214133EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216215840EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216221502EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216223126EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216224743EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216230405EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216232020EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216233635EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190216235249EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217000908EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217002529EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217004144EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217005803EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217011424EA4RMS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RMS-DP!3835.08N/-03-35.08rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz