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
20260910135535EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910135740EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910142603EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910142844EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910145632EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910145939EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910152702EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910153040EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910155732EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910160131EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910162801EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910163159EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910165830EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910170251EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910172900EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910173343EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910175930EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910180439EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910182958EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910183539EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910190026EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910190618EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260910193056EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260910193659EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz