APRS Packet Errors for EA3EG (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
20250913072039EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913072606EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913075139EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913075636EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913082202EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913082706EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913085236EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913085738EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913092300EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913092810EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913095336EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913095841EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913102421EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913102912EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913105444EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913105943EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913112508EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913113014EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913115531EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913120046EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913122556EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913123117EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250913125620EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250913130148EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz