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
20251008214528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251008220028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251008221528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251008223028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251008224528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251008230028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251008231528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251008233028	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251008234528	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009001527	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009003027	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009004527	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009010027	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009011527	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009013027	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009014527	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009020027	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009021527	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009023027	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009024527	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009030027	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009031527	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20251009033027	SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500