Running back, North Carolina A&T, 2021–⁠25

Fredderick Graves

Number
No. 35
Height
5′9″
Weight
225 lb
Class (2025)
Senior
Hometown
Danville, VA

Fredderick Graves played running back at North Carolina A&T (2021–⁠25).

Career highs

106rushing yards, career highvs. Winston-Salem State, 20242rushing touchdowns, career highat William & Mary, 2025

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2021North Carolina A&T5153.005
2022North Carolina A&T683204.7424
2023North Carolina A&T853934.6147
2024North Carolina A&T622253.6116
2025North Carolina A&T1485693.8540
Career3681,5224.11147

Receiving

SeasonTeamRecYdsAvgTDLong
2021North Carolina A&T133.003
2022North Carolina A&T10929.2121
2023North Carolina A&T310.313
2024North Carolina A&T3299.7017
2025North Carolina A&T10878.7018
Career272127.9221

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2021North Carolina A&T35RBYr 1
2022North Carolina A&T35RBYr 2
2023North Carolina A&T35RBYr 3
2024North Carolina A&T35RBYr 4
2025North Carolina A&T35RBSr. (Yr 5)5′9″225

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/playPctileMedianTotalUsage
2022North Carolina A&T (FCS)430.34––14.811%
2025North Carolina A&T (FCS)149-0.0511th (n=576)0.10-8.122%

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). From CollegeFootballData, 2013 on.

Game by game

2025 North Carolina A&T 11 games, 569 rushing yards, 5 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30atTennessee StateL 21–⁠241469140––
Sep 6atUCFL 7–⁠6813190517
Sep 13vs.HamptonW 33–⁠301887122––
Sep 20vs.North Carolina CentralL 20–⁠62926017––
Sep 27atMaineL 30–⁠371347115326
Oct 4atWilliam & MaryL 34–⁠382593221118
Oct 11vs.South Carolina StateL 16–⁠221566033––
Oct 25vs.CampbellW 28–⁠241473021––
Nov 1vs.TowsonL 9–⁠6281808333
Nov 15vs.MonmouthL 19–⁠6312580131−4
Nov 22atElonL 17–⁠557130417
2024 North Carolina A&T 4 games, 225 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 29atWake ForestL 13–⁠451970014––
Sep 7vs.Winston-Salem StateW 27–⁠202610611616
Sep 14vs.DelawareL 13–⁠42143707223
Sep 21atNorth Carolina CentralL 24–⁠6631206––
2023 North Carolina A&T 9 games, 393 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31atUABL 6–⁠351658017––
Sep 9vs.North Carolina CentralL 16–⁠30869147––
Sep 16atElonL 3–⁠271058034––
Sep 30atNorfolk StateW 28–⁠26843021––
Oct 7vs.VillanovaL 14–⁠374006––
Oct 14atDelawareL 6–⁠2120830131−1
Oct 21vs.RichmondL 10–⁠3312290131−1
Oct 28atHamptonL 24–⁠26327020––
Nov 18vs.CampbellL 14–⁠2842601113
2021 North Carolina A&T 1 game, 15 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 10atDukeL 17–⁠455150513

No box score in the source for Sep 25 vs. North Carolina Central, so that game is not listed.

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.