APRS Packet Errors for HL1RR (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
20260110184820	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20260110192914	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20260110201003	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20260110205052	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20260110213140	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20260110221229	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20260110225317	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20260110233407	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz
20260111001454	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-KOREA MMDVM 434.2000 MHz