APRS Packet Errors for EA3ES (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
20260529110116EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260529130300EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260529132128EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260529133327EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260529135202EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260529140353EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260529150446EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260529152404EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz