APRS Packet Errors for YU4EZK (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
20260611023346	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611030402	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611033417	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611040433	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611043449	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611050508	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611053543	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611060600	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611070638	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz
20260611080714	YU4EZK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)YU4EZK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NL MMDVM 433.5500 MHz