APRS Packet Errors for EA9UV (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
20260429164910EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429171944EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429175015EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429182046EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429185116EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429192145EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429195216EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429202244EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429205312EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260429212339EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz