APRS Packet Errors for M6LMT (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
20251112121522M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112124711M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112131926M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112135130M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112142332M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112152725M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112155926M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112163116M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112170308M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz
20251112173500M6LMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6LMT-DP!5133.37N/000-8.78ErRNG0034 IPSC2-DVSPh-F MMDVM 222.3400 MHz