APRS Packet Errors for EA4RCR (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
20181211204743EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211210511EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211213344EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211214921EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211220446EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211222003EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211223533EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211225052EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211230611EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211232130EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211233652EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181211235210EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212000728EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212002245EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212003807EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212005323EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212010844EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212012406EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212013927EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212015444EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212021000EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20181212022519EA4RCR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4RCR-DP!4023.51N/-03-44.47rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz