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
20260209134242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000700Monitoring 146.940MHz
20260209141242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.49N/08752.89W-/A=000748Monitoring 146.940MHz
20260209144242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.49N/08752.89W-/A=000748Monitoring 146.940MHz
20260209151242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000745Monitoring 146.940MHz
20260209154242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000724Monitoring 146.940MHz
20260209161242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000724Monitoring 146.940MHz
20260209164242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000724Monitoring 146.940MHz
20260209171242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000724Monitoring 146.940MHz
20260209174242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000724Monitoring 146.940MHz
20260209181242KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000724Monitoring 146.940MHz
20260209184243KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000724Monitoring 146.940MHz
20260209191243KD9NPQ-1>APIN21,TCPIP*,qAC,T2BC:!4110.48N/08752.89W-/A=000724Monitoring 146.940MHz