APRS Packet Errors for EA2DYQ (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
20191208003415EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208004930EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208010447EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208012002EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208013516EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208015030EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208020547EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208022101EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208023616EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208025131EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208030648EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208032202EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208033716EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208035229EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208040803EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208042319EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208043833EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208045346EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208050903EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208052418EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208053932EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208055446EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208061002EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz
20191208062516EA2DYQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2DYQ-DP!4319.21N/-03-2.16ErRNG0034 IPSC2-EA-Hotspot MMDVM 434.3500 MHz