APRS Packet Errors for EA1IVQ (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
20190121110113EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121111703EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121113301EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121114858EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121120500EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121122052EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121123642EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121125251EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121130844EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121132434EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121134024EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121135628EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121141218EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121142808EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121144403EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121145959EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121151549EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121153141EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121154732EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz
20190121160324EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.73N/-08-37.62rRNG0034 IPSC2-EA1Master MMDVM 431.0750 MHz