APRS Packet Errors for KD9NPQ-1 (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
20260208144237KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000760Monitoring 146.940MHz
20260208151237KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000706Monitoring 146.940MHz
20260208154237KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000706Monitoring 146.940MHz
20260208161238KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.41N/08752.91W-/A=000695Monitoring 146.940MHz
20260208164238KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000835Monitoring 146.940MHz
20260208171238KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000775Monitoring 146.940MHz
20260208174238KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000775Monitoring 146.940MHz
20260208181238KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.47N/08752.89W-112/003/A=000721Monitoring 146.940MHz
20260208184238KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000764Monitoring 146.940MHz
20260208191238KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.49N/08752.89W-/A=000708Monitoring 146.940MHz