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
20260925010631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@010621h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925013631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@013620h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925020631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@020620h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925023631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@023620h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925030631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@030620h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925033631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@033620h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925040631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@040620h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925043631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@043620h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925050631VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@050619h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925053630VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@053619h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925060630VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@060619h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20260925063630VE5BBZ-1>APWW11,TCPIP*,qAC,T2SYDNEY:@063619h0000.00N/00000.00E#PHG3000APRS-IS for Win32