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
20261113004728VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@004717h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113011727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@011717h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113014727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@014717h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113021727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@021717h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113024727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@024717h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113031728VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@031717h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113034727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@034716h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113041727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@041716h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113044727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@044716h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113051727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@051716h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113054727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@054716h0000.00N/00000.00E#PHG3000APRS-IS for Win32
20261113061727VE5BBZ-1>APWW11,TCPIP*,qAC,T2STRAS:@061716h0000.00N/00000.00E#PHG3000APRS-IS for Win32