APRS Packet Errors for VE5BBZ-1 (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
20261109114744VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@114741h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109121744VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@121741h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109124743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@124741h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109131743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@131740h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109134743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@134740h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109141743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@141740h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109144743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@144740h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109151743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@151740h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109154743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@154740h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109161743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@161740h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109164743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@164739h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261109171743VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@171739h0000.00N/00000.00E#PHG3000APRS-IS for Win32