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
20251018015117	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@015105h0000.00N/00000.00ElAPRS-IS for Win32
20251018022117	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@022104h0000.00N/00000.00ElAPRS-IS for Win32
20251018025116	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@025103h0000.00N/00000.00ElAPRS-IS for Win32
20251018032115	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@032102h0000.00N/00000.00ElAPRS-IS for Win32
20251018035114	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@035101h0000.00N/00000.00ElAPRS-IS for Win32
20251018042113	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@042100h0000.00N/00000.00ElAPRS-IS for Win32
20251018045112	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@045059h0000.00N/00000.00ElAPRS-IS for Win32
20251018052111	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@052058h0000.00N/00000.00ElAPRS-IS for Win32
20251018055110	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@055058h0000.00N/00000.00ElAPRS-IS for Win32
20251018062109	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@062057h0000.00N/00000.00ElAPRS-IS for Win32
20251018065109	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@065056h0000.00N/00000.00ElAPRS-IS for Win32
20251018072108	KJ6IJM>APWW11,TCPIP*,qAC,T2BELGIUM:@072055h0000.00N/00000.00ElAPRS-IS for Win32