Receiver, Massachusetts, 2012–⁠15

Rodney Mills

Number
No. 33
Height
6′1″
Hometown
Gainesville, FL

Rodney Mills played receiver at Massachusetts (2012–⁠15).

Career highs

7catches, career highat Toledo, 2014104receiving yards, career highvs. Temple, 20152receiving touchdowns, career hightwice; last vs. Temple, 2015

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2013Massachusetts5479.4025
2014Massachusetts3048916.3572
2015Massachusetts3347714.5362
Career681,01314.9872

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
20121101
2013N12336
2014E9 of 12134

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played); E, ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2012Massachusetts33WR
2013Massachusetts33WR
2014Massachusetts33WR
2015Massachusetts33WR6′1″

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
2013Massachusetts60.52––3.1–
2014Massachusetts570.5149th (n=496)0.5229.36%
2015Massachusetts610.3422nd (n=465)0.5320.69%

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

2015 Massachusetts 9 games, 33 catches, 477 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Sep 19vs.TempleL 23–⁠255104248–
Oct 10atBowling GreenL 38–⁠626100029–
Oct 17vs.Kent StateL 10–⁠15496062–
Oct 24vs.ToledoL 35–⁠51216110–
Oct 31atBall StateL 10–⁠20445027–
Nov 7vs.AkronL 13–⁠17662023–
Nov 14atEastern MichiganW 28–⁠171707–
Nov 21vs.Miami (OH)L 13–⁠20438017–
Nov 27atBuffaloW 31–⁠261909–
2014 Massachusetts 12 games, 30 catches, 489 yards, 5 TD
DateOpponentResultRecYdsTDLongRush
Aug 30vs.Boston CollegeL 7–⁠30122022–
Sep 6vs.ColoradoL 38–⁠41114114–
Sep 13atVanderbiltL 31–⁠34376253–
Sep 20atPenn StateL 7–⁠481707–
Sep 27vs.Bowling GreenL 42–⁠47261132–
Oct 4atMiami (OH)L 41–⁠42564126–
Oct 11atKent StateW 40–⁠17441015–
Oct 18vs.Eastern MichiganW 36–⁠14229015–
Oct 25atToledoL 35–⁠42754018–
Nov 12vs.Ball StateW 24–⁠10118018–
Nov 18atAkronL 6–⁠30172072–
Nov 28vs.BuffaloL 21–⁠41231027–
2013 Massachusetts 4 games, 5 catches, 47 yards
DateOpponentResultRecYdsTDLongRush
Sep 14atKansas StateL 7–⁠37214010–
Nov 2vs.Northern IllinoisL 19–⁠63125025–
Nov 23atCentral MichiganL 0–⁠371000−2
Nov 29atOhioL 23–⁠511808–

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.