APRS Packet Errors for MB6SG (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
20250411145602	MB6SG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6SG-DP!5122.80N/000-4.80ErRNG0034 IPSC2-DVSPh-F MMDVM 144.8250 MHz
20250411152804	MB6SG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6SG-DP!5122.80N/000-4.80ErRNG0034 IPSC2-DVSPh-F MMDVM 144.8250 MHz
20250411173700	MB6SG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6SG-DP!5122.80N/000-4.80ErRNG0034 IPSC2-DVSPh-F MMDVM 144.8250 MHz
20250411180915	MB6SG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6SG-DP!5122.80N/000-4.80ErRNG0034 IPSC2-DVSPh-F MMDVM 144.8250 MHz
20250411184121	MB6SG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6SG-DP!5122.80N/000-4.80ErRNG0034 IPSC2-DVSPh-F MMDVM 144.8250 MHz
20250411191327	MB6SG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6SG-DP!5122.80N/000-4.80ErRNG0034 IPSC2-DVSPh-F MMDVM 144.8250 MHz
20250411194542	MB6SG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6SG-DP!5122.80N/000-4.80ErRNG0034 IPSC2-DVSPh-F MMDVM 144.8250 MHz
20250411201748	MB6SG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6SG-DP!5122.80N/000-4.80ErRNG0034 IPSC2-DVSPh-F MMDVM 144.8250 MHz