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
20260325030503	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz
20260325034553	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz
20260325042640	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz
20260325050730	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz
20260325054819	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz
20260325062914	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz
20260325071005	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz
20260325075055	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz
20260325083144	HL1RR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)HL1RR-DP!12300.00N/45600.00rRNG0034 IPSC2-KOREA MMDVM 438.0250 MHz