Receiver, Utah State, 2006–⁠09

Nnamdi Gwacham

Number
No. 81
Height
6′3″
Hometown
Chino Hills, CA

Nnamdi Gwacham played receiver at Utah State (2006–⁠09).

Career highs

140receiving yards, career highvs. Nevada, 2009

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2006*Utah State11616.0016
2007*Utah State155.005
2008*Utah State2037018.5262
2009Utah State1523615.7177
Career3762716.9377

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
2006Utah State81WR
2007Utah State81WR
2008Utah State81WR
2009Utah State81WR6′3″

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

2009 Utah State 7 games, 15 catches, 236 yards, 1 TD
DateOpponentResultRecYdsTDLong
Sep 19atTexas A&ML 30–⁠3821308
Sep 26vs.Southern UtahW 53–⁠34559022
Oct 2atBYUL 17–⁠351909
Oct 10atNew Mexico StateL 17–⁠201303
Oct 17vs.NevadaL 32–⁠354140177
Oct 24vs.Louisiana TechW 23–⁠211606
Oct 31atFresno StateL 27–⁠311606
2008 Utah State 10 games, 20 catches, 370 yards, 2 TD
DateOpponentResultRecYdsTDLong
Aug 30atUNLVL 17–⁠271616
Sep 6atOregonL 24–⁠66339018
Sep 20vs.IdahoW 42–⁠171606
Oct 3vs.BYUL 14–⁠34234021
Oct 18atNevadaL 17–⁠44331012
Oct 25vs.Fresno StateL 28–⁠30272052
Nov 1vs.Hawai’iW 30–⁠14162162
Nov 8atBoise StateL 14–⁠49337016
Nov 15atLouisiana TechL 38–⁠45376039
Nov 29vs.New Mexico StateW 47–⁠21707
2007 Utah State 1 game, 1 catch, 5 yards
DateOpponentResultRecYdsTDLong
Sep 8atWyomingL 18–⁠321505
2006 Utah State 1 game, 1 catch, 16 yards
DateOpponentResultRecYdsTDLong
Oct 21atLouisiana TechL 35–⁠48116016

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.