APRS Packet Errors for KE8BII-4 (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
20260524140650KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@140650h0000.00N/00000.00ElAPRS-IS for Win32
20260524143650KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@143651h0000.00N/00000.00ElAPRS-IS for Win32
20260524150651KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@150652h0000.00N/00000.00ElAPRS-IS for Win32
20260524153652KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@153653h0000.00N/00000.00ElAPRS-IS for Win32
20260524160652KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@160653h0000.00N/00000.00ElAPRS-IS for Win32
20260524163653KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@163654h0000.00N/00000.00ElAPRS-IS for Win32
20260524170653KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@170654h0000.00N/00000.00ElAPRS-IS for Win32
20260524173654KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@173655h0000.00N/00000.00ElAPRS-IS for Win32
20260524180655KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@180656h0000.00N/00000.00ElAPRS-IS for Win32
20260524183655KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@183656h0000.00N/00000.00ElAPRS-IS for Win32
20260524190656KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@190657h0000.00N/00000.00ElAPRS-IS for Win32
20260524193656KE8BII-4>APWW11,TCPIP*,qAC,T2BC:@193657h0000.00N/00000.00ElAPRS-IS for Win32