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
20250726040655EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726042616EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726043722EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726045655EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726050749EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726052736EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726053817EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726055828EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726060845EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726062928EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726063914EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726070024EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726070943EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726073101EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726074012EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726080158EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726081041EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726083257EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726084111EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726090337EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726091140EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250726093430EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250726094209EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz