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
20250411144102EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411150321EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411151135EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411153352EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411154159EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411160424EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411161235EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411163455EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411164320EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411170526EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411171342EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411173556EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411174417EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411180628EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411181441EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411183659EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411184524EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411190729EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411191601EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411193758EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411194651EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20250411200825EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20250411201741EA3EG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3EG-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz