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
20251208081455	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@081453h0000.00N/00000.00ElAPRS-IS for Win32
20251208084454	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@084452h0000.00N/00000.00ElAPRS-IS for Win32
20251208091453	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@091451h0000.00N/00000.00ElAPRS-IS for Win32
20251208094452	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@094450h0000.00N/00000.00ElAPRS-IS for Win32
20251208101451	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@101449h0000.00N/00000.00ElAPRS-IS for Win32
20251208104450	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@104448h0000.00N/00000.00ElAPRS-IS for Win32
20251208111450	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@111449h0000.00N/00000.00ElAPRS-IS for Win32
20251208114449	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@114448h0000.00N/00000.00ElAPRS-IS for Win32
20251208121448	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@121447h0000.00N/00000.00ElAPRS-IS for Win32
20251208124447	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@124446h0000.00N/00000.00ElAPRS-IS for Win32
20251208131446	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@131445h0000.00N/00000.00ElAPRS-IS for Win32
20251208134445	KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@134444h0000.00N/00000.00ElAPRS-IS for Win32