APRS Packet Errors for M9PCW (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
20260612151009M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612154201M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612161353M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612164712M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612174937M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612182129M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612185319M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612192510M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612195703M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260612202856M9PCW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M9PCW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz