APRS Packet Errors for N9PTZ (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
20250207142538	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250207150615	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250207154651	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250207162729	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250207170817	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250207174844	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250207182923	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250207191000	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250207195052	N9PTZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N9PTZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz