APRS Packet Errors for EA3GLC (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
20250701045057EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701052126EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701055205EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701062234EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701065314EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701072343EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701075424EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701082453EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701092612EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz
20250701095652EA3GLC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3GLC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA3Master MMDVM 433.0000 MHz