clock menu more-arrow no yes

Filed under:

Chiefs Beat Vikings: Five Bad Stats

New, comments
Getty Images

The Kansas City Chiefs beat the Minnesota Vikings which means finding five good stats was pretty easy. There were some bad stats, too, but they don't seem so bad when the Chiefs win.

I did my best finding five bad stats for the Chiefs Week 4 victory over the Vikings:

0. Number of Chiefs rushing touchdowns. Actually, I'm putting this here because the Chiefs have no rushing touchdowns on the year (H/T chiefsfanindonkeyland). The No. 1 rushing attack last year and through one month the haven't hit the end zone on the ground. They're the only NFL team without a rushing touchdown this year.

1. Number of Chiefs touchdowns. Hey, I'm not going to complain much during a win but kicking five field goals isn't always a good thing. It would've been nice to see the Chiefs convert at least one more of those into a touchdown. 

3.7. Yards per rush on the day for the Chiefs. It's not a terrible number -- they had 103 yards on 28 carries. But it's just...an average day. We'll go ahead and insert the obligatory "Chiefs really miss Jamaal Charles" line here. We say that a lot, but it's true.

102. Yards by the Vikings tight ends. That comes on nine catches from Visanthe Shiancoe (58) and Kyle Rudolph (44). We talked about this before the game because Minnesota has a pair of good tight ends. Luckily, it wasn't the 

67. Number of yards rushing by Percy Harvin. Nothing annoys me more than seeing an end around fool the Chiefs, especially a pair of 23-yard runs. They weren't backbreakers but those are so frustrating because you can see early on in the play whether the Chiefs defense is going to bite.