APRS Packet Errors for EA1IBH (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
20191113132449EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113134012EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113135532EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113141051EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113142611EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113144134EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113145653EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113151214EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113152735EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113154259EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113155821EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113161342EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113162903EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113164427EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113165949EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113171510EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113173034EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113174559EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113180121EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113181645EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113183208EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113184735EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113190259EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz
20191113191824EA1IBH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1IBH-DP!4321.52N/-08-25.22rRNG0034 IPSC2-EA-Hotspot MMDVM 430.4000 MHz