Receiver, Colorado, 2013–⁠17

Bryce Bobo

Number
No. 4
Height
6′2″
Weight
200 lb
Hometown
Covina, CA

Bryce Bobo played receiver at Colorado (2013–⁠17).

Career highs

10catches, career hightwice; last vs. USC, 2017126receiving yards, career highat Oregon State, 20172receiving touchdowns, career hightwice; last at Oregon State, 2017

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2014Colorado232159.3338
2015Colorado242078.6023
2016Colorado4454812.5266
2017Colorado6269311.2538
Career1531,66310.91066

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHtWt
2013Colorado4WR
2014Colorado4WR
2015Colorado4WR
2016Colorado4WR
2017Colorado4WR6′2″200

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
2014Colorado310.5453rd (n=496)0.5216.74%
2015Colorado370.3827th (n=465)0.5314.05%
2016Colorado590.7075th (n=489)0.5241.56%
2017Colorado960.5353rd (n=507)0.5251.110%

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

2017 Colorado 12 games, 62 catches, 693 yards, 5 TD
DateOpponentResultRecYdsTDLongRush
Sep 1vs.Colorado StateW 17–⁠3849014–
Sep 9vs.Texas StateW 37–⁠3775128–
Sep 16vs.Northern ColoradoW 41–⁠21677129–
Sep 23vs.WashingtonL 10–⁠37229016–
Sep 30atUCLAL 23–⁠272230129
Oct 7vs.ArizonaL 42–⁠45653114–
Oct 14atOregon StateW 36–⁠339126238–
Oct 21atWashington StateL 0–⁠28219012–
Oct 28vs.CaliforniaW 44–⁠28334020–
Nov 4atArizona StateL 30–⁠41342019–
Nov 11vs.USCL 24–⁠3810113027–
Nov 25atUtahL 13–⁠34453028–
2016 Colorado 12 games, 44 catches, 548 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 2vs.Colorado StateW 44–⁠7599046–
Sep 10vs.Idaho StateW 56–⁠72707–
Sep 17atMichiganL 28–⁠45150050–
Sep 24atOregonW 41–⁠38572131–
Oct 1vs.Oregon StateW 47–⁠6420010–
Oct 8atUSCL 17–⁠211083121–
Oct 15vs.Arizona StateW 40–⁠166110066–
Oct 22atStanfordW 10–⁠5227019–
Nov 3vs.UCLAW 20–⁠1027010–
Nov 12atArizonaW 49–⁠24319010–
Nov 19vs.Washington StateW 38–⁠24129029–
Dec 29 ✦vs.Oklahoma StateL 8–⁠38325012–
2015 Colorado 9 games, 24 catches, 207 yards
DateOpponentResultRecYdsTDLongRush
Sep 12vs.MassachusettsW 48–⁠14113013–
Sep 26vs.NichollsW 48–⁠0114014–
Oct 3vs.OregonL 24–⁠4121307–
Oct 10atArizona StateL 23–⁠48429010–
Oct 17vs.ArizonaL 31–⁠38651016–
Oct 24atOregon StateW 17–⁠1321408–
Oct 31atUCLAL 31–⁠3521308–
Nov 7vs.StanfordL 10–⁠42429012–
Nov 28atUtahL 14–⁠20231023–
2014 Colorado 9 games, 23 catches, 215 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Sep 6atMassachusettsW 41–⁠38554021–
Sep 13vs.Arizona StateL 24–⁠3831808–
Sep 20vs.Hawai’iW 21–⁠1231707–
Sep 27atCaliforniaL 56–⁠59236130–
Oct 4vs.Oregon StateL 31–⁠36217010–
Oct 25vs.UCLAL 37–⁠40454238–
Nov 1vs.WashingtonL 23–⁠381303–
Nov 8atArizonaL 20–⁠381505−3
Nov 22atOregonL 10–⁠4421107–

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.