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
20261010143217VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@143203h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010150217VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@150203h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010153217VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@153203h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010160217VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@160203h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010163217VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@163202h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010170217VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@170202h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010173217VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@173202h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010180217VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@180202h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010183216VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@183202h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010190216VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@190202h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010193216VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@193202h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261010200216VE5BBZ-1>APWW11,TCPIP*,qAC,T2PERTH:@200201h0000.00N/00000.00E#PHG3000APRS-IS for Win32