APRS Packet Errors for W1WOW (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
20240427212412W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240427215455W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240427222540W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240427225620W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240427232701W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240427235800W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240428002858W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240428005955W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240428020135W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz
20240428023227W1WOW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)W1WOW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-NEWENGLAND MMDVM 438.5000 MHz