APRS Packet Errors for PU1LDD (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
20250917132503	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz
20250917135550	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz
20250917142636	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz
20250917152810	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz
20250917155857	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz
20250917162943	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz
20250917170030	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz
20250917173119	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz
20250917180211	PU1LDD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)PU1LDD-DP!22-0.00S/043-0.00WrRNG0034 IPSC2-BRASIL-2 MMDVM 438.8350 MHz