APRS Packet Errors for SV9FBT-15 (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
20251215124530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215130031SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215131530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215133030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215134530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215140030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215141531SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215143030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215144530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215150030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215151530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215153030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215154530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215160030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215161530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215163031SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215164530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215170030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215171530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215173030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215174531SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215180030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215181530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251215183030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500