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
20251205201648KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@201639h0000.00N/00000.00ElAPRS-IS for Win32
20251205204647KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@204638h0000.00N/00000.00ElAPRS-IS for Win32
20251205211646KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@211637h0000.00N/00000.00ElAPRS-IS for Win32
20251205214645KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@214636h0000.00N/00000.00ElAPRS-IS for Win32
20251205221644KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@221635h0000.00N/00000.00ElAPRS-IS for Win32
20251205224644KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@224634h0000.00N/00000.00ElAPRS-IS for Win32
20251205231643KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@231633h0000.00N/00000.00ElAPRS-IS for Win32
20251205234642KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@234632h0000.00N/00000.00ElAPRS-IS for Win32
20251206001641KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@001631h0000.00N/00000.00ElAPRS-IS for Win32
20251206004640KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@004630h0000.00N/00000.00ElAPRS-IS for Win32
20251206011639KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@011629h0000.00N/00000.00ElAPRS-IS for Win32
20251206014638KJ6IJM>APWW11,TCPIP*,qAC,T2CAEAST:@014628h0000.00N/00000.00ElAPRS-IS for Win32