APRS Packet Errors for G7UYD (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
20251218032801G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218035935G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218043107G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218050239G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218053410G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218060608G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218063752G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218070936G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218074122G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20251218081309G7UYD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G7UYD-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz