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
20251025204914	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@204900h0000.00N/00000.00ElAPRS-IS for Win32
20251025211913	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@211859h0000.00N/00000.00ElAPRS-IS for Win32
20251025214913	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@214859h0000.00N/00000.00ElAPRS-IS for Win32
20251025221912	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@221858h0000.00N/00000.00ElAPRS-IS for Win32
20251025224911	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@224857h0000.00N/00000.00ElAPRS-IS for Win32
20251025231910	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@231856h0000.00N/00000.00ElAPRS-IS for Win32
20251025234909	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@234855h0000.00N/00000.00ElAPRS-IS for Win32
20251026001909	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@001854h0000.00N/00000.00ElAPRS-IS for Win32
20251026004908	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@004854h0000.00N/00000.00ElAPRS-IS for Win32
20251026011907	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@011853h0000.00N/00000.00ElAPRS-IS for Win32
20251026014906	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@014852h0000.00N/00000.00ElAPRS-IS for Win32
20251026021905	KJ6IJM>APWW11,TCPIP*,qAC,T2PERTH:@021851h0000.00N/00000.00ElAPRS-IS for Win32