APRS Packet Errors for G4XTZ (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
20241123111620G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123114658G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123121743G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123124823G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123131904G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123134944G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123142026G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123152146G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123155228G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz
20241123162310G4XTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4XTZ-DP!5131.20N/000-37.50rRNG0034 IPSC2-FreeSTAR MMDVM 433.8750 MHz