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
20260208145212REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st87F N7YSE Red Knoll
20260208152221REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st85F N7YSE Red Knoll
20260208155238REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st86F N7YSE Red Knoll
20260208162252REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st87F N7YSE Red Knoll
20260208165308REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st89F N7YSE Red Knoll
20260208172318REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st91F N7YSE Red Knoll
20260208175332REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st92F N7YSE Red Knoll
20260208182345REDKNL>APOT30,WIDE2-2,qAR,BLOW:!S;an%2#Co# st94F N7YSE Red Knoll
20260208185358REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st99F N7YSE Red Knoll
20260208192407REDKNL>APOT30,WIDE2-2,qAR,KA7HOS-10:!S;an%2#Co# st99F N7YSE Red Knoll
20260208195417REDKNL>APOT30,WIDE2-2,qAR,UTAH:!S;an%2#Co# st101F N7YSE Red Knoll
20260208202434REDKNL>APOT30,WIDE2-2,qAR,KA7HOS-10:!S;an%2#Co# st105F N7YSE Red Knoll