APRS Packet Errors for K2LJL (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
20251202235953K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@235952h0000.00N/00000.00ElAPRS-IS for Win32
20251203002953K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@002953h0000.00N/00000.00ElAPRS-IS for Win32
20251203005954K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@005953h0000.00N/00000.00ElAPRS-IS for Win32
20251203012954K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@012954h0000.00N/00000.00ElAPRS-IS for Win32
20251203015954K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@015954h0000.00N/00000.00ElAPRS-IS for Win32
20251203022955K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@022955h0000.00N/00000.00ElAPRS-IS for Win32
20251203025955K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@025955h0000.00N/00000.00ElAPRS-IS for Win32
20251203032955K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@032955h0000.00N/00000.00ElAPRS-IS for Win32
20251203035956K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@035955h0000.00N/00000.00ElAPRS-IS for Win32
20251203042956K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@042955h0000.00N/00000.00ElAPRS-IS for Win32
20251203045956K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@045956h0000.00N/00000.00ElAPRS-IS for Win32
20251203052956K2LJL>APWW11,TCPIP*,qAC,T2CHILE:@052956h0000.00N/00000.00ElAPRS-IS for Win32