APRS Packet Errors for WK1B-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
20260208164352WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@164351h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208171352WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@171351h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208174352WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@174351h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208181352WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@181351h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208184352WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@184351h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208191352WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@191352h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208194352WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@194352h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208201353WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@201352h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208204353WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@204352h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208211353WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@211352h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208214353WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@214352h3039.15N/08144.41WlPHG3000APRS-IS for Win32
20260208221353WK1B-1>APWW11,TCPIP*,qAC,T2SYDNEY:@221353h3039.15N/08144.41WlPHG3000APRS-IS for Win32