APRS Packet Errors for M7UFX (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
20251226173947M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226181142M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226184337M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226191535M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226194733M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226201929M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226212312M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226215501M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226222646M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz
20251226225830M7UFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7UFX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.8000 MHz