APRS Packet Errors for KB3TZD (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
20260208131141KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@131138h4102.82N7615.74W-PHG2000
20260208134142KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@134139h4102.82N7615.74W-PHG2000
20260208141143KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@141140h4102.82N7615.74W-PHG2000
20260208144143KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@144140h4102.82N7615.74W-PHG2000
20260208151144KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@151141h4102.82N7615.74W-PHG2000
20260208154144KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@154141h4102.82N7615.74W-PHG2000
20260208161145KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@161141h4102.82N7615.74W-PHG2000
20260208164145KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@164142h4102.82N7615.74W-PHG2000
20260208171146KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@171142h4102.82N7615.74W-PHG2000
20260208174147KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@174143h4102.82N7615.74W-PHG2000
20260208181147KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@181144h4102.82N7615.74W-PHG2000
20260208184148KB3TZD>APWW11,TCPIP*,qAC,SEVENTH:@184144h4102.82N7615.74W-PHG2000