Running back, East Carolina, 2011–⁠15

Chris Hairston

Number
No. 22
Height
6′0″
Hometown
Winston-Salem , NC

Chris Hairston played running back at East Carolina (2011–⁠15).

At a glance

Best season
754
Rushing yards, 2015 (East Carolina, 5–⁠7)
Best game
154 yards
Vs. Towson, week 1, 2015: No. 3 rushing game in FBS that week

Career highs

154rushing yards, career highvs. Towson, 20154rushing touchdowns, career highvs. Towson, 20156catches, career highat Navy, 2015

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2013East Carolina491863.8325
2014East Carolina795286.7254
2015East Carolina1657544.6845
Career2931,4685.01354

Receiving

SeasonTeamRecYdsAvgTDLong
2013East Carolina66010.0018
2014East Carolina6315.2011
2015East Carolina291936.7136
Career412846.9136

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2011East Carolina22RB
2012East Carolina22RB
2013East Carolina22RB
2014East Carolina22RB
2015East Carolina22RB6′0″

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
2013East Carolina36-0.05––-1.77%–
2014East Carolina890.1869th (n=253)0.1216.310%0.24
2015East Carolina1950.0733rd (n=268)0.1212.722%0.01

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

2015 East Carolina 12 games, 754 rushing yards, 8 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 5vs.TowsonW 28–⁠201815445190
Sep 12atFloridaL 24–⁠31171505340
Sep 19atNavyL 21–⁠45103806300
Sep 26vs.Virginia TechW 35–⁠281530–––
Oct 3atSMUW 49–⁠2318911130
Oct 10atBYUL 38–⁠45157713500
Oct 17vs.TulsaW 30–⁠17188201121
Oct 22vs.TempleL 14–⁠2486513110
Oct 30atUConnL 13–⁠3112660–––
Nov 7vs.South FloridaL 17–⁠2213240–––
Nov 19atUCFW 44–⁠71412312140
Nov 28vs.CincinnatiL 16–⁠1971603200
2014 East Carolina 11 games, 528 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30vs.North Carolina CentralW 52–⁠73330–––
Sep 6atSouth CarolinaL 23–⁠336351100
Sep 20vs.North CarolinaW 70–⁠415580–––
Oct 4vs.SMUW 45–⁠24125311−10
Oct 11atSouth FloridaW 28–⁠173200–––
Oct 23vs.UConnW 31–⁠21370–––
Nov 1atTempleL 10–⁠202115303250
Nov 13atCincinnatiL 46–⁠54350–––
Nov 28atTulsaW 49–⁠326910–––
Dec 4vs.UCFL 30–⁠32–––170
Jan 3 ✦vs.FloridaL 20–⁠2817730–––
2013 East Carolina 8 games, 186 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 5vs.Florida AtlanticW 31–⁠135811180
Sep 28atNorth CarolinaW 55–⁠31451–––
Oct 5atMiddle TennesseeW 24–⁠17189404350
Oct 12atTulaneL 33–⁠36410170
Oct 19vs.Southern MissW 55–⁠146321–––
Nov 9vs.TulsaW 58–⁠242−10–––
Nov 16vs.UABW 63–⁠149480–––
Nov 23atNC StateW 42–⁠281−10–––

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.