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
20260405104121EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405104159EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405111211EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405111231EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405114303EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405114304EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405121333EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405121402EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405124403EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405124435EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405131434EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405131523EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405134503EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405134618EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405141534EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405141702EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405144605EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405144803EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405151636EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405151907EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405154706EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405154945EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20260405161737EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20260405162044EA3ES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ES-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz