APRS Packet Errors for OZ4JK (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
20261002173306	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002180325	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002183343	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002190359	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002193416	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002200433	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002203450	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002210507	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002213523	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz
20261002220539	OZ4JK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ4JK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.0000 MHz