Receiver, Tulsa, 2014–⁠18

Justin Hobbs

Number
No. 29
Height
6′4″
Weight
230 lb
Class (2018)
Senior
Hometown
Overland Park, KS

Justin Hobbs played receiver at Tulsa (2014–⁠18).

Career highs

9catches, career hightwice; last at Temple, 2018150receiving yards, career highat SMU, 2015

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2015Tulsa3255117.2261
2016Tulsa5068513.7444
2017Tulsa5583015.1369
2018Tulsa3948012.3349
Career1762,54614.51269

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2014Tulsa29WRRS
2015Tulsa29WRFr.
2016Tulsa29WRSo.
2017Tulsa29WRJr.
2018Tulsa29WRSr.6′4″230

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.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2015Tulsa500.8693rd (n=465)0.5342.96%
2016Tulsa800.6365th (n=489)0.5250.57%
2017Tulsa890.4843rd (n=507)0.5242.311%
2018Tulsa720.2814th (n=497)0.5319.99%

Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.

Game by game

2018 Tulsa 11 games, 39 catches, 480 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Sep 1vs.Central ArkansasW 38–⁠27361149–
Sep 8atTexasL 21–⁠28213014–
Sep 15vs.Arkansas StateL 20–⁠29122022–
Sep 20atTempleL 17–⁠31978015–
Oct 4atHoustonL 26–⁠41482027–
Oct 20atArkansasL 0–⁠23212010–
Oct 27vs.TulaneL 17–⁠24425012–
Nov 3vs.UConnW 49–⁠19245127–
Nov 10atMemphisL 21–⁠47559128–
Nov 17atNavyL 29–⁠37223018–
Nov 24vs.SMUW 27–⁠24560031–
2017 Tulsa 11 games, 55 catches, 830 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Aug 31atOklahoma StateL 24–⁠59671024–
Sep 9vs.LouisianaW 66–⁠425103169–
Sep 16atToledoL 51–⁠54568039–
Sep 23vs.New MexicoL 13–⁠16793034–
Sep 30vs.NavyL 21–⁠31455031–
Oct 7atTulaneL 28–⁠62259159–
Oct 21atUConnL 14–⁠20996026–
Oct 27atSMUL 34–⁠383141060–
Nov 3vs.MemphisL 14–⁠41557027–
Nov 16atSouth FloridaL 20–⁠27641019–
Nov 25vs.TempleL 22–⁠43346135–
2016 Tulsa 13 games, 50 catches, 685 yards, 4 TD
DateOpponentResultRecYdsTDLongRush
Sep 3vs.San José StateW 45–⁠10330112–
Sep 10atOhio StateL 3–⁠48333015–
Sep 17vs.North Carolina A&TW 58–⁠217114032–
Sep 24atFresno StateW 48–⁠41564123–
Oct 7vs.SMUW 43–⁠40219011–
Oct 15atHoustonL 31–⁠388129138–
Oct 22vs.TulaneW 50–⁠27217010–
Oct 29atMemphisW 59–⁠30340020–
Nov 5vs.East CarolinaW 45–⁠24334016–
Nov 12atNavyL 40–⁠425123044–
Nov 19atUCFW 35–⁠20332015–
Nov 25vs.CincinnatiW 40–⁠37322114–
Dec 19 ✦vs.Central MichiganW 55–⁠10328014–
2015 Tulsa 11 games, 32 catches, 551 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 19atOklahomaL 38–⁠52117017–
Oct 3vs.HoustonL 24–⁠381808–
Oct 10vs.UL MonroeW 34–⁠24582136–
Oct 17atEast CarolinaL 17–⁠30357032–
Oct 23vs.MemphisL 42–⁠663410246
Oct 31atSMUW 40–⁠317150061–
Nov 7vs.UCFW 45–⁠30238031–
Nov 14atCincinnatiL 38–⁠494700343
Nov 21vs.NavyL 21–⁠442330224
Nov 27atTulaneW 45–⁠34120120–
Dec 26 ✦vs.Virginia TechL 52–⁠55335018–

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.