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
20251208233800EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251208235049EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209000825EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209002132EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209003850EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209005205EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209010914EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209012255EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209013939EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209015341EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209021005EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209022438EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209024030EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209025542EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209031055EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209032630EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209034119EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209035716EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209041144EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209042801EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209044208EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251209045842EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251209051234EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz