APRS Packet Errors for M1BZM (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
20250916191829M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916194839M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916201849M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916204859M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916211908M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916214918M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916221928M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916224937M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916231946M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz
20250916234955M1BZM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)M1BZM-DP!5130.11N/000-8.53ErRNG0034 IPSC2-DVSPh-D MMDVM 50.6000 MHz