Running back, Oklahoma State, 2008–⁠10

Bryant Ward

Number
No. 37
Height
5′11″
Hometown
Stillwater, OK

Bryant Ward played running back at Oklahoma State (2008–⁠10).

Honors

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2008*Oklahoma State111.011
2009Oklahoma State144.004
2010Oklahoma State111.001
Career362.014

Returns

SeasonTeamKRYdsTD
2009Oklahoma State4410

Receiving

SeasonTeamRecYdsAvgTDLong
2009Oklahoma State111.001
2010Oklahoma State4174.3014
Career5183.6014

Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.

Defense before 2016

SeasonGSoloAstTkl
20085516
20098729
20106325
On file15520

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2008Oklahoma State37RB
2009Oklahoma State37RB
2010Oklahoma State37RB5′11″

As each season’s roster listed the player (CollegeFootballData). Classes before the latest listing are counted back from it; “Yr 1” is the year on file where that count can’t place a season he played (a redshirt, transfer or 2020 year); height and weight as last listed.

Game by game

2010 Oklahoma State 3 games, 1 rushing yard
DateOpponentResultCarRush ydsRush TDKRYds
Sep 30vs.Texas A&MW 38–⁠35–––––
Oct 30atKansas StateW 24–⁠14–––––
Nov 20atKansasW 48–⁠14110––
2009 Oklahoma State 4 games, 4 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 12vs.HoustonL 35–⁠45–––112
Sep 19vs.RiceW 41–⁠24–––225
Sep 26vs.GramblingW 56–⁠6140––
Oct 31vs.TexasL 14–⁠41–––14
2008 Oklahoma State 1 game, 1 rushing yard, 1 TD
DateOpponentResultCarRush ydsRush TDKRYds
Nov 1vs.Iowa StateW 59–⁠17111––

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

Is this you, or do you know of something wrong or missing here? Suggest a correction. We check each one against a source before changing the page.