Running back, Texas Tech, 2008–⁠11

Harrison Jeffers

Lettered 2009–⁠10 (school media guide)

Number
No. 10
Height
5′7″
Hometown
Lawton, OK

Harrison Jeffers played running back at Texas Tech (2008–⁠11).

Career highs

3rushing touchdowns, career highvs. New Mexico, 20096catches, career highvs. Kansas State, 200990receiving yards, career highvs. New Mexico, 2009

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2009Texas Tech352176.2435
2010Texas Tech18995.5032
Career533166.0435

Receiving

SeasonTeamRecYdsAvgTDLong
2009Texas Tech272188.1162
2010Texas Tech2168.0011
Career292348.1162

Returns

SeasonTeamKRYdsTD
2010Texas Tech61010

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009Texas Tech10RB
2010Texas Tech10RB
2011Texas Tech10RB5′7″

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 Texas Tech 6 games, 6 returns, 101 yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 11atNew MexicoW 52–⁠177440–––
Oct 23atColoradoW 27–⁠241−40–––
Nov 6vs.MissouriW 24–⁠17270–––
Nov 13atOklahomaL 7–⁠45100–––
Nov 20vs.Weber StateW 64–⁠2163602160
Jan 1 ✦vs.NorthwesternW 45–⁠381160–––
2009 Texas Tech 11 games, 217 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 5vs.North DakotaW 38–⁠1321605390
Sep 12vs.RiceW 55–⁠105230120
Sep 26atHoustonL 28–⁠2945712130
Oct 3vs.New MexicoW 48–⁠2882935901
Oct 10vs.Kansas StateW 66–⁠1475506470
Oct 17atNebraskaW 31–⁠102190480
Oct 24vs.Texas A&ML 30–⁠52380270
Oct 31vs.KansasW 42–⁠21160–––
Nov 14atOklahoma StateL 17–⁠24130–––
Nov 28vs.BaylorW 20–⁠131−30–––
Jan 2 ✦vs.Michigan StateW 41–⁠311402120

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.