APRS Packet Errors for K2AH-7 (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
20260505001636K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>359/000/A=000000K2AH HT
20260505002733K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>359/000/A=000000K2AH HT
20260505003804K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>359/000/A=000000K2AH HT
20260505010912K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>359/000/A=000000K2AH HT
20260505013057K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>152/000/A=000000K2AH HT
20260505014111K2AH-7>APAT81-1,PICURS,TAOSKI*,WIDE2,qAO,KA8JMW-10:!0000.00N/00000.00W>152/000/A=000000K2AH HT
20260505015143K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>152/000/A=000000K2AH HT
20260505020256K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>152/000/A=000000K2AH HT
20260505021429K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>152/000/A=000000K2AH HT
20260505022447K2AH-7>APAT81-1,PICURS*,WIDE2-1,qAO,KA8JMW-10:!0000.00N/00000.00W>152/000/A=000000K2AH HT