APRS Packet Errors for VE3KAE (last 24 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
20241121194504VE3KAE>APWW11,TCPIP*,qAC,T2TAS:@194443h0000.00N/00000.00ElAPRS-IS for Win32
20241121194505VE3KAE>APWW11,TCPIP*,qAC,T2TAS:@194503h0000.00N/00000.00ElAPRS-IS for Win32
20241121200519VE3KAE>APWW11,TCPIP*,qAC,T2CAEAST:@200519h0000.00N/00000.00ElAPRS-IS for Win32
20241121201433VE3KAE>APWW11,TCPIP*,qAC,T2CSNGRAD:@201433h0000.00N/00000.00ElAPRS-IS for Win32
20241121204434VE3KAE>APWW11,TCPIP*,qAC,T2CSNGRAD:@204434h0000.00N/00000.00ElAPRS-IS for Win32
20241121211434VE3KAE>APWW11,TCPIP*,qAC,T2CSNGRAD:@211434h0000.00N/00000.00ElAPRS-IS for Win32
20241121214435VE3KAE>APWW11,TCPIP*,qAC,T2CSNGRAD:@214434h0000.00N/00000.00ElAPRS-IS for Win32
20241121221435VE3KAE>APWW11,TCPIP*,qAC,T2CSNGRAD:@221435h0000.00N/00000.00ElAPRS-IS for Win32
20241122004921VE3KAE>APWW11,TCPIP*,qAC,T2TAS:@004846h0000.00N/00000.00ElAPRS-IS for Win32
20241122004922VE3KAE>APWW11,TCPIP*,qAC,T2TAS:@004921h0000.00N/00000.00ElAPRS-IS for Win32
20241122010922VE3KAE>APWW11,TCPIP*,qAC,T2SPAIN:@010922h0000.00N/00000.00ElAPRS-IS for Win32
20241122013922VE3KAE>APWW11,TCPIP*,qAC,T2SPAIN:@013922h0000.00N/00000.00ElAPRS-IS for Win32