APRS Packet Errors for SV9FBT-12 (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
20251214091532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214093032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214094532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214100032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214101532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214103032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214104532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214110032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214111532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214113032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214114532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214120032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214121531SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214123032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214124531SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214130032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214131532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214133032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214134532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214140032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214141532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214143032SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214144532SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000
20251214150031SV9FBT-12>APRS,TCPIP*,qAC,SV9FBT-11:!350.48N/02540.10ErWelcome to HBLINK RX: 438.175000 TX: 438.175000