Fullback, Miami (OH), 2009–⁠12

Justin Semmes

Number
No. 46
Height
6′2″
Hometown
Clarkston, MI

Justin Semmes played fullback at Miami (OH) (2009–⁠12).

Career highs

100rushing yards, career highvs. Akron, 20112rushing touchdowns, career highvs. Akron, 2011

Team titles: MAC champions, 2010

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2010Miami (OH)133.003
2011Miami (OH)411704.1217
2012Miami (OH)16503.1115
Career582233.8317

Receiving

SeasonTeamRecYdsAvgTDLong
2010Miami (OH)3124.016
2011Miami (OH)8799.9319
2012Miami (OH)22110.5011
Career131128.6419

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009Miami (OH)46FB
2010Miami (OH)46FB
2011Miami (OH)46FB
2012Miami (OH)46FB6′2″

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

2012 Miami (OH) 6 games, 50 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 1atOhio StateL 10–⁠5651301100
Sep 8vs.Southern IllinoisW 30–⁠142501110
Sep 15atBoise StateL 12–⁠39140–––
Sep 22vs.MassachusettsW 27–⁠16170–––
Sep 29atAkronW 56–⁠496201–––
Nov 17atCentral MichiganL 16–⁠30110–––
2011 Miami (OH) 7 games, 170 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 3atMissouriL 6–⁠17210–––
Oct 8vs.ArmyW 35–⁠28–––2251
Oct 15atKent StateW 9–⁠3–––170
Oct 22atToledoL 28–⁠49–––2161
Oct 29vs.BuffaloW 41–⁠13–––2251
Nov 3vs.AkronW 35–⁠3241002160
Nov 9atTempleL 21–⁠2415690–––
2010 Miami (OH) 4 games, 3 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 18vs.Colorado StateW 31–⁠10–––161
Sep 25atMissouriL 13–⁠51130–––
Dec 3vs.Northern IllinoisW 26–⁠21–––120
Jan 6 ✦vs.Middle TennesseeW 35–⁠21–––140

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.