APRS Packet Errors for 9M2SYK-8 (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
202602091332149M2SYK-8>APOT30,WIDE1-1,qAO,9M4GTD:!0312.36N10144.26EP104/000/A=000238LoRa APRS TRACKER
202602091402339M2SYK-8>APOT30,WIDE1-1,qAO,9W2BWS:!0312.36N10144.26EP104/000/A=000237LoRa APRS TRACKER
202602091432519M2SYK-8>APOT30,WIDE1-1,qAO,9M4GTD:!0312.36N10144.26EP104/000/A=000262LoRa APRS TRACKER
202602091503099M2SYK-8>APOT30,WIDE1-1,qAO,9W2BWS:!0312.36N10144.26EP104/000/A=000240LoRa APRS TRACKER
202602091533289M2SYK-8>APOT30,WIDE1-1,qAO,9W2BWS:!0312.36N10144.26EP104/000/A=000258LoRa APRS TRACKER
202602091603459M2SYK-8>APOT30,WIDE1-1,qAO,9W2BWS:!0312.36N10144.26EP104/000/A=000261LoRa APRS TRACKER
202602091634039M2SYK-8>APOT30,WIDE1-1,qAO,9W2BWS:!0312.36N10144.26EP104/000/A=000253LoRa APRS TRACKER
202602091704219M2SYK-8>APOT30,WIDE1-1,qAO,9M4GTD:!0312.36N10144.26EP104/000/A=000262LoRa APRS TRACKER
202602091734399M2SYK-8>APOT30,WIDE1-1,qAO,9M4GTD:!0312.36N10144.26EP104/000/A=000258LoRa APRS TRACKER
202602091804569M2SYK-8>APOT30,WIDE1-1,qAO,9M4GTD:!0312.36N10144.26EP104/000/A=000263LoRa APRS TRACKER
202602091835139M2SYK-8>APOT30,WIDE1-1,qAO,9M4GTD:!0312.36N10144.26EP104/000/A=000248LoRa APRS TRACKER
202602091905319M2SYK-8>APOT30,WIDE1-1,qAO,9M4GTD:!0312.36N10144.26EP104/000/A=000261LoRa APRS TRACKER