APRS Packet Errors for KJ6IJM (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
20251202231858	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@231855h0000.00N/00000.00ElAPRS-IS for Win32
20251202234857	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@234854h0000.00N/00000.00ElAPRS-IS for Win32
20251203001857	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@001853h0000.00N/00000.00ElAPRS-IS for Win32
20251203004856	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@004852h0000.00N/00000.00ElAPRS-IS for Win32
20251203011855	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@011851h0000.00N/00000.00ElAPRS-IS for Win32
20251203014854	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@014850h0000.00N/00000.00ElAPRS-IS for Win32
20251203021853	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@021849h0000.00N/00000.00ElAPRS-IS for Win32
20251203024852	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@024848h0000.00N/00000.00ElAPRS-IS for Win32
20251203031851	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@031847h0000.00N/00000.00ElAPRS-IS for Win32
20251203034850	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@034846h0000.00N/00000.00ElAPRS-IS for Win32
20251203041849	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@041845h0000.00N/00000.00ElAPRS-IS for Win32
20251203044848	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@044844h0000.00N/00000.00ElAPRS-IS for Win32