APRS Packet Errors for M0JIW (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
20251018015721	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251018033155	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251018040324	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251018043455	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251018050626	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251018053758	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251018060929	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251018064105	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20251018071250	M0JIW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M0JIW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz