Running back, Ball State, 2013–⁠16

Teddy Williamson

Number
No. 6
Height
5′9″
Hometown
O’Fallon, MO

Teddy Williamson played running back at Ball State (2013–⁠16).

Career highs

80rushing yards, career highvs. Miami (OH), 2013

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2013Ball State692273.3118
2014Ball State24562.3016
2015Ball State401363.4012
2016Ball State401814.5223
Career1736003.5323

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Ball State640000

Receiving

SeasonTeamRecYdsAvgTDLong
2013Ball State242.003
2015Ball State231.507
2016Ball State6406.7012
Career10474.7012

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2013Ball State6RB
2014Ball State6RB
2015Ball State6RB
2016Ball State6RB5′9″

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
2013Ball State70-0.183rd (n=226)0.07-12.410%-0.08
2014Ball State23-0.43––-10.04%–
2015Ball State42-0.05––-2.19%–
2016Ball State470.20––9.35%0.14

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 Ball State 11 games, 181 rushing yards, 2 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 2atGeorgia StateW 31–⁠21428115––
Sep 10atIndianaL 20–⁠301707––
Sep 17vs.Eastern KentuckyW 41–⁠14942112––
Sep 24atFlorida AtlanticW 31–⁠272603––
Oct 1vs.Northern IllinoisL 24–⁠31––––13
Oct 8atCentral MichiganL 21–⁠2441205––
Oct 15atBuffaloW 31–⁠21839023––
Nov 1vs.Western MichiganL 20–⁠523603220
Nov 8vs.Eastern MichiganL 41–⁠4883701119
Nov 16atToledoL 19–⁠37––––28
Nov 22atMiami (OH)L 20–⁠211404––
2015 Ball State 6 games, 136 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 3vs.VMIW 48–⁠3616740121−4
Sep 12atTexas A&ML 23–⁠5671609––
Oct 10atNorthern IllinoisL 41–⁠5921005––
Oct 24vs.Central MichiganL 21–⁠23110117
Nov 5atWestern MichiganL 7–⁠542605––
Nov 24vs.Bowling GreenL 10–⁠48122908––
2014 Ball State 7 games, 56 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30vs.ColgateW 30–⁠10732016––
Oct 11vs.Western MichiganL 38–⁠421303––
Oct 18atCentral MichiganW 32–⁠291202––
Oct 25vs.AkronW 35–⁠216−103––
Nov 12atMassachusettsL 10–⁠242504––
Nov 22vs.Eastern MichiganW 45–⁠3061308––
Nov 28atBowling GreenW 41–⁠241202––
2013 Ball State 10 games, 227 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 29vs.Illinois StateW 51–⁠281505––
Sep 7vs.ArmyW 40–⁠14135801824
Sep 14atNorth TexasL 27–⁠346102––
Sep 21atEastern MichiganW 51–⁠201131013––
Oct 19atWestern MichiganW 38–⁠174001––
Oct 26atAkronW 42–⁠24524012––
Nov 6vs.Central MichiganW 44–⁠2461405––
Nov 13atNorthern IllinoisL 27–⁠481000––
Nov 29vs.Miami (OH)W 55–⁠14198019––
Jan 5 ✦vs.Arkansas StateL 20–⁠2331407––

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.