APRS Packet Errors for OZ1CD (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
20251015083715	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz
20251015090755	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz
20251015093835	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz
20251015100915	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz
20251015103956	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz
20251015111038	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz
20251015114113	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz
20251015121140	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz
20251015124209	OZ1CD>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1CD-DP!3756.81N/000-45.11rRNG0034 IPSC2-DK MMDVM 433.3250 MHz