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
20250911221745W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250911225752W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250911233759W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250912001826W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250912005904W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250912013922W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250912022002W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250912030029W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz
20250912034117W9WSS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W9WSS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-CLAND MMDVM 441.0000 MHz