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
20251013231530	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251013233030	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251013234530	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014001528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014003028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014004528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014010028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014011528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014013028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014014528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014020028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014021528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014023028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014024528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014030028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014031528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014033028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014034528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014040028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251014041528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500