APRS Packet Errors for KD2TCQ-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
20251008222935KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@222936h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251008225936KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@225936h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251008232937KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@232937h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251008235937KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@235937h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251009002938KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@002938h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251009005938KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@005938h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251009012939KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@012938h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251009015940KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@015939h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251009022941KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@022940h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251009025941KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@025941h0000.00N/00000.00E#PHG7000APRS-IS for Win32
20251009032942KD2TCQ-10>APWW11,TCPIP*,qAC,T2CSNGRAD:@032942h0000.00N/00000.00E#PHG7000APRS-IS for Win32