APRS Packet Errors for KD4JLY-5 (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
20251123013017KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@013017h0000.00N/00000.00E#APRS-IS for Win32
20251123020017KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@020017h0000.00N/00000.00E#APRS-IS for Win32
20251123023018KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@023018h0000.00N/00000.00E#APRS-IS for Win32
20251123030019KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@030018h0000.00N/00000.00E#APRS-IS for Win32
20251123033019KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@033019h0000.00N/00000.00E#APRS-IS for Win32
20251123040020KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@040020h0000.00N/00000.00E#APRS-IS for Win32
20251123043021KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@043020h0000.00N/00000.00E#APRS-IS for Win32
20251123050022KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@050021h0000.00N/00000.00E#APRS-IS for Win32
20251123053022KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@053022h0000.00N/00000.00E#APRS-IS for Win32
20251123060023KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@060023h0000.00N/00000.00E#APRS-IS for Win32
20251123063024KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@063023h0000.00N/00000.00E#APRS-IS for Win32
20251123070024KD4JLY-5>APWW11,TCPIP*,qAC,T2SPAIN:@070024h0000.00N/00000.00E#APRS-IS for Win32