APRS Packet Errors for M0VUB (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
20241121081219M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20241121084253M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20241121101431M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20241121104506M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20241121111540M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20241121114618M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20241121121653M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20241121124729M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20241121131806M0VUB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0VUB-DP!5100.00N/001-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz