APRS Packet Errors for DO2BY (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
20260325025933DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325033018DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325043144DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325050227DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325053310DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325060355DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325063441DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325070526DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325073612DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz
20260325080657DO2BY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO2BY-DP!28431.20S/65047.52rRNG0034 IPSC2-DMR-DL MMDVM 430.6500 MHz