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
20251219202839SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219204338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219205838SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219211338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219212838SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219214338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219215838SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219221338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219222839SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219224338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219225838SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219231338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219232838SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219234338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251219235838SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220001338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220002839SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220004338SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220005838SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220011530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220013031SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220014530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220020031SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251220021531SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500