APRS Packet Errors for EA4GAX (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
20260223062028EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223065101EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223072143EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223075225EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223082305EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223085353EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223092435EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223095533EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223102619EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz
20260223105700EA4GAX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GAX-DP!3800.00N/095-0.00WrRNG0034 IPSC2-EA4Master MMDVM 434.0000 MHz