APRS Packet Errors for EA4CZR (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
20190923122038EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923123547EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923125056EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923130607EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923132120EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923133630EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923140650EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923142204EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923143713EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923145223EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923150733EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923152245EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923153755EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923155304EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923160816EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923162329EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923163838EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923165349EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923170900EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923172413EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923173922EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923175433EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz
20190923180942EA4CZR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4CZR-DP!4014.92N/-03-49.74rRNG0034 IPSC2-EA1Master MMDVM 430.8500 MHz