APRS Packet Errors for OZ1GHK (last 24 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
20251215083052	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz
20251215090112	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz
20251215093130	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz
20251215100149	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz
20251215103209	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz
20251215110230	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz
20251215120307	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz
20251215123326	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz
20251215133403	OZ1GHK>APZDMR,QTH,TCPIP*,qAU,T2DENMARK:)OZ1GHK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DK MMDVM 433.0125 MHz