APRS Packet Errors for W9WSS (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
20250902165528	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250902173546	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250902181604	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250902185620	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250902193648	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250902201718	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250902205733	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250902213739	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250902221757	W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz