APRS Packet Errors for EA9UV (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
20260403193326EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260403200358EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260403203429EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260403210501EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260403213533EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260403220604EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260403223634EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260403230704EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260403233732EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20260404000801EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz