APRS Packet Errors for M1ABY (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
20251219193351M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251219200429M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251219203506M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251219210544M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251219213621M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251219220657M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251219223733M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251219230810M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251219233846M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz
20251220000925M1ABY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1ABY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-USA MMDVM 438.6750 MHz