APRS Packet Errors for HB9HTS-41 (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
20260208134253HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208141314HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208144335HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208151356HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208154418HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208161439HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208164500HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208171521HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208174542HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208181604HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208184625HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778
20260208191646HB9HTS-41>APRSGW,TCPIP*,qAR,HB9HTS-41:!4720.13N/00828.45E2/B=100/A=001778