APRS Packet Errors for REDKNL (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
20260209085934REDKNL>APOT30,WIDE2-2,qAR,BLOW:!S;an%2#Co# st90F N7YSE Red Knoll
20260209092946REDKNL>APOT30,WIDE2-2,qAR,BLOW:!S;an%2#Co# st89F N7YSE Red Knoll
20260209100000REDKNL>APOT30,WIDE2-2,qAR,KA7HOS-10:!S;an%2#Co# st89F N7YSE Red Knoll
20260209103015REDKNL>APOT30,WIDE2-2,qAR,KA7HOS-10:!S;an%2#Co# st89F N7YSE Red Knoll
20260209110027REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st88F N7YSE Red Knoll
20260209113038REDKNL>APOT30,WIDE2-2,qAR,KA7HOS-10:!S;an%2#Co# st88F N7YSE Red Knoll
20260209120052REDKNL>APOT30,WIDE2-2,qAR,KA7HOS-10:!S;an%2#Co# st88F N7YSE Red Knoll
20260209123104REDKNL>APOT30,WIDE2-2,qAR,KA7HOS-10:!S;an%2#Co# st87F N7YSE Red Knoll
20260209130113REDKNL>APOT30,WIDE2-2,qAR,KA7HOS-10:!S;an%2#Co# st86F N7YSE Red Knoll
20260209133125REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st86F N7YSE Red Knoll
20260209140139REDKNL>APOT30,WIDE2-2,qAR,BLOW:!S;an%2#Co# st86F N7YSE Red Knoll
20260209143149REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st87F N7YSE Red Knoll