Running back, Maryland, 2012–⁠16

Wes Brown

Number
No. 4
Height
6′1″
Hometown
Baltimore, MD

Wes Brown played running back at Maryland (2012–⁠16).

Career highs

121rushing yards, career highvs. NC State, 20122rushing touchdowns, career highvs. Iowa, 2014

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2012Maryland903824.2222
2014Maryland1033563.5633
2015Maryland713174.5319
2016Maryland33250.809
Career2971,0803.61133

Receiving

SeasonTeamRecYdsAvgTDLong
2012Maryland5142.807
2014Maryland211989.4038
2015Maryland13896.8024
2016Maryland813617.0039
Career474379.3039

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2012Maryland4RB
2013Maryland4RB
2014Maryland4RB
2015Maryland4RB
2016Maryland4RB6′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/playPctileMedianTotalUsageAdj. rush
2014Maryland1070.1767th (n=253)0.1218.515%0.28
2015Maryland930.1042nd (n=268)0.128.914%0.06
2016Maryland40-0.10––-4.29%-0.17

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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Game by game

2016 Maryland 7 games, 25 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Oct 1vs.PurdueW 50–⁠75201200
Oct 29atIndianaL 36–⁠423140–––
Nov 5atMichiganL 3–⁠595−402530
Nov 12vs.Ohio StateL 3–⁠629101150
Nov 19atNebraskaL 7–⁠2831301180
Nov 26vs.RutgersW 31–⁠137−502160
Dec 26 ✦vs.Boston CollegeL 30–⁠361401140
2015 Maryland 10 games, 317 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 5vs.RichmondW 50–⁠21137411−30
Sep 12vs.Bowling GreenL 27–⁠4895302280
Sep 19vs.South FloridaW 35–⁠17130–––
Sep 26atWest VirginiaL 6–⁠4531303260
Oct 3vs.MichiganL 0–⁠285802260
Oct 10atOhio StateL 28–⁠495301–––
Oct 24vs.Penn StateL 30–⁠315170350
Oct 31atIowaL 15–⁠318330130
Nov 7vs.WisconsinL 24–⁠3110341140
Nov 14atMichigan StateL 7–⁠2412520–––
2014 Maryland 12 games, 356 rushing yards, 6 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30vs.James MadisonW 52–⁠7138102270
Sep 6atSouth FloridaW 24–⁠1713610–––
Sep 20atSyracuseW 34–⁠20260170
Sep 27atIndianaW 37–⁠15153402500
Oct 4vs.Ohio StateL 24–⁠522813150
Oct 18vs.IowaW 38–⁠318192140
Oct 25atWisconsinL 7–⁠5252202120
Nov 1atPenn StateW 20–⁠19102411130
Nov 15vs.Michigan StateL 15–⁠379504120
Nov 22atMichiganW 23–⁠16113911170
Nov 29vs.RutgersL 38–⁠4194203270
Dec 30 ✦vs.StanfordL 21–⁠4561511140
2012 Maryland 7 games, 382 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 8atTempleW 36–⁠277500170
Sep 15vs.UConnL 21–⁠2414741–––
Sep 22atWest VirginiaL 21–⁠31230–––
Oct 6vs.Wake ForestW 19–⁠14102302130
Oct 20vs.NC StateL 18–⁠20251211–––
Oct 27atBoston CollegeL 17–⁠20237302−60
Nov 3vs.Georgia TechL 13–⁠339380–––

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.