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
20190222011641DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222013350DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222015111DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222020821DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222022602DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222024519DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222030339DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222032050DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222033749DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222035501DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222041203DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222042921DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222044615DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222050327DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222052017DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222053704DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222055418DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222061119DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222062818DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222064522DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz
20190222070254DG5NEK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DG5NEK-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 439.9750@-9.9 MHz