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
20250912060237EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250912060620EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250912062013EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250912063302EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250912063640EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250912070329EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250912070651EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250912080425EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250912080724EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250912090519EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250912090755EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250912100614EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250912100817EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250912110709EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250912110838EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250912112656EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250912113737EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250912113849EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA3Master MMDVM 436.0000@-0.0 MHz
20250912115731EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz