APRS Packet Errors for KG4FJC-10 (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
20260208183133KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260208190132KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260208193133KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260208200132KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260208210133KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260208213132KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260208220132KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260208223132KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260208230132KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater
20260209000132KG4FJC-10>APDW16,TCPIP*,qAC,T2OREGON:!3740.21N7828.22W&APRS Digipeater