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
20190320074631EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320080301EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320081931EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320083611EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320085241EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320090911EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320092542EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320094216EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320095845EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320101513EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320103144EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320104815EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320110452EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320112122EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320113751EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320115424EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320121057EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320122729EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320124358EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320130032EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320131705EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190320133335EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz