APRS Packet Errors for KF0QWD-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
20260318190617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318193617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318200617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318203617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318210617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318213617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318220617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318223617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318230617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260318233617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260319000617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO
20260319003617KF0QWD-10>APBPQ1,TCPIP*,qAC,T2CAEAST:!0300.39N285.105W&LinBPQ BBS Node Woodland Park CO