Receiver, Baylor, 2006–⁠09

Justin Fenty

Lettered 2006–⁠08 (school media guide)

Number
No. 23
Height
5′9″
Hometown
Denton, TX

Justin Fenty played receiver at Baylor (2006–⁠09).

Career highs

7catches, career highat Colorado, 2006

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2006*Baylor191839.6119
2007*Baylor181548.6027
2008*Baylor6508.3113
Career433879.0227

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
2006Baylor23WR
2007Baylor23WR
2008Baylor23WR
2009Baylor23WR5′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

2009 Baylor 1 game, 1 return, 18 yards
DateOpponentResultRecYdsTDLongRush
Sep 26vs.Northwestern StateW 68–⁠13–––––
2008 Baylor 4 games, 6 catches, 50 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 6vs.Northwestern StateW 51–⁠621016–
Oct 11vs.Iowa StateW 38–⁠10110010–
Oct 25atNebraskaL 20–⁠32221013–
Nov 8atTexasL 21–⁠451909–
2007 Baylor 7 games, 18 catches, 154 yards
DateOpponentResultRecYdsTDLongRush
Sep 1atTCUL 0–⁠27535015–
Sep 8vs.RiceW 42–⁠17111011–
Sep 15vs.Texas StateW 34–⁠27353027–
Sep 22atBuffaloW 34–⁠21315085
Oct 20vs.TexasL 10–⁠3132309–
Nov 10atOklahomaL 21–⁠5221208–
Nov 17vs.Oklahoma StateL 14–⁠451505–
2006 Baylor 7 games, 19 catches, 183 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 16atWashington StateL 15–⁠175651193
Sep 23vs.ArmyL 20–⁠273240183
Sep 30vs.Kansas StateW 17–⁠3114014–
Oct 7atColoradoW 34–⁠31752019–
Oct 14atTexasL 31–⁠63219014–
Oct 21vs.KansasW 36–⁠35––––−6
Nov 11atOklahoma StateL 24–⁠661909–

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.