APRS Packet Errors for M3YGQ (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
20250915151033M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915154215M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915161406M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915164546M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915171737M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915174931M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915182112M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915185252M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915192431M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20250915195621M3YGQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M3YGQ-DP!5254.75N/000-40.98rRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz