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
20251213174654EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213180943EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213181723EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213184043EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213191130EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213191819EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213194232EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213194845EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213201327EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213201910EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213204415EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213204937EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213211504EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213212004EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213214551EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213215029EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213221636EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213222054EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213224723EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213225120EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20251213231810EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20251213232144EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz