APRS Packet Errors for EA4RO (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
20190421164647EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421170345EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421172112EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421173821EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421175514EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421181219EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421182917EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421184638EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421190401EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421192058EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421193756EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421195503EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421201153EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421202843EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421204546EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421210253EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421212013EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421213707EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421215355EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421221058EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421222753EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421224451EA4RO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RO-DP!4022.80N/-03-44.12rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz