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
20251206204000M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251206211150M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251206214335M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251206221520M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251206231847M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251206235028M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251207002209M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251207005351M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251207012533M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz
20251207015715M7LPN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M7LPN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8250 MHz