Receiver, Colorado State, 2008–⁠10

Tyson Liggett

Number
No. 23
Height
5′9″
Hometown
Limon, CO

Tyson Liggett played receiver at Colorado State (2008–⁠10).

Career highs

11catches, career highat BYU, 2009156receiving yards, career highat BYU, 2009

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2008*Colorado State3217.0011
2009Colorado State1725314.9340
2010Colorado State413809.3026
Career6165410.7340

Returns

SeasonTeamPRYdsTD
2010Colorado State10110

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.

On the roster

SeasonTeamNo.PosHt
2008Colorado State23WR
2009Colorado State23WR
2010Colorado State23WR5′9″

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 Colorado State 11 games, 41 catches, 380 yards
DateOpponentResultRecRec ydsRec TDPR
Sep 4vs.ColoradoL 3–⁠243270–
Sep 11atNevadaL 6–⁠517460–
Sep 18atMiami (OH)L 10–⁠313200–
Sep 25vs.IdahoW 36–⁠344510–
Oct 2vs.TCUL 0–⁠2732004
Oct 9atAir ForceL 27–⁠4952502
Oct 16vs.UNLVW 43–⁠1021001
Oct 30vs.New MexicoW 38–⁠142330–
Nov 6atSan Diego StateL 19–⁠2446002
Nov 13vs.BYUL 10–⁠495620–
Nov 20atWyomingL 0–⁠4432601
2009 Colorado State 5 games, 17 catches, 253 yards, 3 TD
DateOpponentResultRecRec ydsRec TDPR
Sep 26atBYUL 23–⁠42111561–
Oct 3atIdahoL 29–⁠312291–
Oct 17atTCUL 6–⁠44120–
Oct 24vs.San Diego StateL 28–⁠421401–
Oct 31vs.Air ForceL 16–⁠342260–
2008 Colorado State 3 games, 3 catches, 21 yards
DateOpponentResultRecRec ydsRec TDPR
Oct 18atUtahL 16–⁠491110–
Oct 25atSan Diego StateW 38–⁠34170–
Dec 20 ✦vs.Fresno StateW 40–⁠35130–

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.