APRS Packet Errors for EA2TU-DP (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
20260208182902EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208185938EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208193012EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208200046EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208203119EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208210150EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208213221EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208220252EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208223323EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz
20260208230353EA2TU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2TU-DP!4329.44N/00332.52WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.0000 MHz