APRS Packet Errors for EA1BL (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
20251219135247EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219142318EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219145352EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219152425EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219155458EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219162532EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219165603EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219172636EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219175709EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz
20251219182744EA1BL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1BL-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 433.5500 MHz