APRS Packet Errors for KB5LNC-17 (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
20251123013639KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@013638h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123020639KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@020638h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123023639KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@023638h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123030639KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@030638h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123033639KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@033638h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123040640KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@040639h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123043641KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@043639h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123050641KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@050640h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123053641KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@053640h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123060642KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@060641h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123063642KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@063641h0000.00N/00000.00ElAPRS-IS_D for Win32
20251123070642KB5LNC-17>APWW11,TCPIP*,qAC,T2NUERNBG:@070641h0000.00N/00000.00ElAPRS-IS_D for Win32