APRS Packet Errors for M6CMG (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
20250325230645	M6CMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6CMG-DP!5307.20N/000-19.80rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20250325233729	M6CMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6CMG-DP!5307.20N/000-19.80rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20250326000809	M6CMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6CMG-DP!5307.20N/000-19.80rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20250326003847	M6CMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6CMG-DP!5307.20N/000-19.80rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20250326010926	M6CMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6CMG-DP!5307.20N/000-19.80rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20250326014005	M6CMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6CMG-DP!5307.20N/000-19.80rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20250326021044	M6CMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6CMG-DP!5307.20N/000-19.80rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20250326024121	M6CMG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M6CMG-DP!5307.20N/000-19.80rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz