APRS Packet Errors for K2ACD (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
20260209104657K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209111657K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209114657K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209121658K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209124658K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209131658K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209134657K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209141658K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209144657K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209151657K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209154657K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com
20260209161657K2ACD>APDW16,TCPIP*,qAC,T2OREGON:!X9z+G;q7b& !K2ACD igate - http://n7mky.com