Running back, Troy, 2016–⁠19

Jabir Daughtry-Frye

Number
No. 5
Height
5′7″
Weight
173 lb
Class (2019)
Junior
Hometown
Pensacola, FL

Jabir Daughtry-Frye played running back at Troy (2016–⁠19).

Career highs

140rushing yards, career highvs. Coastal Carolina, 2018

Team titles: Sun Belt champions, 2017

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2016Troy201397.0166
2017Troy1−4−4.000
2018Troy533717.0274
2019Troy331464.4217
Career1076526.1574

Returns

SeasonTeamKRYdsTDPRYdsTD
2016Troy2055811120
2017Troy1160–––
2018Troy1332901130
2019Troy81940–––
Career421,09712250

Receiving

SeasonTeamRecYdsAvgTDLong
2016Troy6335.5010
2018Troy2223510.7135
2019Troy10909.0039
Career383589.4139

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

On the roster

SeasonTeamNo.PosClassHtWt
2016Troy5RBYr 1
2017Troy5RBYr 2
2018Troy5RBYr 3
2019Troy5RBJr. (Yr 4)5′7″173

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
2017Troy1-1.89––-1.9––
2018Troy750.3391st (n=300)0.1524.89%0.12
2019Troy490.05––2.510%0.02

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

2019 Troy 8 games, 146 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDKRYdsPR
Aug 31vs.CampbellW 43–⁠143130129–
Sep 14vs.Southern MissL 42–⁠47130279–
Oct 16vs.South AlabamaW 37–⁠136260–––
Oct 26atGeorgia StateL 33–⁠525200–––
Nov 2atCoastal CarolinaL 35–⁠363121240–
Nov 9vs.Georgia SouthernW 49–⁠286370–––
Nov 16atTexas StateW 63–⁠279351227–
Nov 29vs.App StateL 13–⁠48–––119–
2018 Troy 13 games, 371 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDKRYdsPR
Sep 1vs.Boise StateL 20–⁠567411–––
Sep 8vs.Florida A&MW 59–⁠77710––1
Sep 15atNebraskaW 24–⁠196150–––
Sep 22atUL MonroeW 35–⁠271240–––
Sep 29vs.Coastal CarolinaW 45–⁠2151401135–
Oct 4vs.Georgia StateW 37–⁠206160247–
Oct 13atLibertyL 16–⁠22260396–
Oct 23atSouth AlabamaW 38–⁠17430–––
Nov 3vs.LouisianaW 26–⁠168280475–
Nov 10atGeorgia SouthernW 35–⁠212180114–
Nov 17vs.Texas StateW 12–⁠73110262–
Nov 24atApp StateL 10–⁠211−40–––
Dec 22 ✦vs.BuffaloW 42–⁠32120–––
2017 Troy 1 game, −4 rushing yards
DateOpponentResultCarRush ydsRush TDKRYdsPR
Sep 2atBoise StateL 13–⁠241−40116–
2016 Troy 8 games, 139 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDKRYdsPR
Sep 3vs.Austin PeayW 57–⁠175330378–
Sep 10atClemsonL 24–⁠304611114–
Sep 17atSouthern MissW 37–⁠312−20388–
Sep 24vs.New Mexico StateW 52–⁠635021261
Oct 1atIdahoW 34–⁠13–––119–
Oct 20atSouth AlabamaW 28–⁠213220368–
Nov 5vs.MassachusettsW 52–⁠3132004110–
Nov 12vs.App StateW 28–⁠24–––355–

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.