APRS Packet Errors for DG5NEK (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
20191017231547DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191017233106DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191017234623DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018000144DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018001701DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018003219DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018004736DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018010258DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018011818DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018013342DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018014902DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018020427DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018021946DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018023506DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018025026DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018030547DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018032104DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018033621DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018035137DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018040658DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018042215DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018043733DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz
20191018045257DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9625@-9.4 MHz