APRS Packet Errors for M7LPN (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
20250702094926M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702102109M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702105307M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702112445M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702115700M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702122839M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702130038M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702133255M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702140513M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20250702143749M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz