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
20250816115029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816120530SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816122029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816123529SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816125029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816130529SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816132029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816133529SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816135029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816140529SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816142030SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816143529SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816145029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816150529SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816152029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816153529SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816155029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816160529SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816162029SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816164212SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816165712SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816171212SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500
20250816174054SV9FBT-15>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 145.387500 TX: 145.387500