APRS Packet Errors for KQ4BUD-10 (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
20260209150048KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@150048h3606.87N/08537.91WlAPRS-IS for Win32
20260209153049KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@153049h3606.87N/08537.91WlAPRS-IS for Win32
20260209160049KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@160049h3606.87N/08537.91WlAPRS-IS for Win32
20260209163050KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@163050h3606.87N/08537.91WlAPRS-IS for Win32
20260209170051KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@170050h3606.87N/08537.91WlAPRS-IS for Win32
20260209173051KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@173051h3606.87N/08537.91WlAPRS-IS for Win32
20260209180051KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@180051h3606.87N/08537.91WlAPRS-IS for Win32
20260209183052KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@183051h3606.87N/08537.91WlAPRS-IS for Win32
20260209190052KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@190052h3606.87N/08537.91WlAPRS-IS for Win32
20260209193052KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@193052h3606.87N/08537.91WlAPRS-IS for Win32
20260209200053KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@200052h3606.87N/08537.91WlAPRS-IS for Win32
20260209203054KQ4BUD-10>APWW11,TCPIP*,qAC,T2PANAMA:@203053h3606.87N/08537.91WlAPRS-IS for Win32