APRS Packet Errors for OV5JAM (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
20260126040053	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126043115	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126050136	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126053159	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126060221	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126070307	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126073329	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126080351	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126083415	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz
20260126090439	OV5JAM>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OV5JAM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 434.5000 MHz