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
20190217215658EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190217221322EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190217222944EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190217224605EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190217230225EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190217231843EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190217233502EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190217235124EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218000742EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218002402EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218004022EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218005643EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218011301EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218012921EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218014540EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218020200EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218021817EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218023435EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218025052EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218030715EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218032334EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218033953EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz
20190218035610EA1IVQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IVQ-DP!4225.70N/-08-37.92rRNG0034 IPSC2-EA1Master MMDVM 438.1750 MHz