APRS Packet Errors for DB1IG (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
20261019093308DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019100357DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019103447DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019110537DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019113629DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019120721DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019123813DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019130905DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019133957DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz
20261019141049DB1IG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DB1IG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DMR-DL MMDVM 438.8000 MHz