APRS Packet Errors for DO2NMB (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
20200524155148DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20200524162224DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20200524165259DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20200524172335DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20200524185526DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20200524192604DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20200524195638DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20200524202713DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20200524205747DO2NMB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2NMB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz