APRS Packet Errors for M7TST (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
20250816120156M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816123317M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816130434M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816133636M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816140811M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816143950M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816151112M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816154247M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816161413M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz
20250816171830M7TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7TST-DP!5217.58N/000-41.88rRNG0034 IPSC2-FreeSTAR MMDVM 448.8000 MHz