Running back, Richmond, 2024–⁠26

Aziz Foster-Powell

Number
No. 3
Height
5′9″
Weight
218 lb
Class (2026)
Senior
Hometown
Richmond, VA

Aziz Foster-Powell plays running back for Richmond. Last time out, at Fordham: 12 carries, 68 yards; 2 catches, 8 yards. Foster-Powell leads Richmond in rushing touchdowns and rushing yards this season.

2026 so far

534 rushing yards, 6 TD

Last game: 12 carries, 68 yards; 2 catches, 8 yards at Fordham, L 14–⁠20

Next game: vs. Colgate, Oct 24

Game by game this season, rushing yards
  1. 108BUCK
  2. 34@HOW
  3. -1@NCSU
  4. 87GTWN
  5. 125FUR
  6. 113@LAF
  7. 68@FOR

Filled bars: wins; outlined: losses.

Career highs

125rushing yards, career highvs. Furman, 20262rushing touchdowns, career hightwice; last vs. Georgetown, 2026

Team titles: Coastal Athletic Association champions, 2024

Rushing

Rushing yards, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Richmond562304.1122
2025Richmond1255684.5427
2026Richmond1025345.2633
Career2831,3324.71133

Receiving

SeasonTeamRecYdsAvgTDLong
2024Richmond3103.307
2025Richmond15916.1127
2026Richmond1717310.2133
Career352747.8233

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Richmond3RBSo.
2025Richmond3RBJr.
2026Richmond3RBSr.5′9″218

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
2025Richmond (FCS)1530.0023rd (n=576)0.100.619%
2026Richmond (FCS)1180.2480th (n=478)0.1028.724%

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

2026 Richmond 7 games, 534 rushing yards, 6 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 29vs.BucknellW 35–⁠1415108233238
Sep 5atHowardW 28–⁠21103419242
Sep 11atNC StateL 0–⁠731−100––
Sep 19vs.GeorgetownW 24–⁠211787233535
Sep 26vs.FurmanW 13–⁠925125017130
Oct 3atLafayetteW 40–⁠3122113123520
Oct 10atFordhamL 14–⁠20126802028
2025 Richmond 12 games, 568 rushing yards, 4 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30atLehighL 14–⁠2193208––
Sep 6atWoffordW 14–⁠1011370142−4
Sep 13atNorth CarolinaL 6–⁠411238010––
Sep 20vs.VMIW 38–⁠1472018111
Sep 27vs.HowardW 13–⁠125130617
Oct 4atBucknellL 28–⁠338108027––
Oct 11atColgateW 24–⁠19122707––
Oct 18vs.Holy CrossL 22–⁠281380116215
Nov 1vs.FordhamW 17–⁠141562015440
Nov 8atGeorgetownW 31–⁠24126411939
Nov 15vs.LafayetteL 28–⁠35127011616
Nov 22atWilliam & MaryW 28–⁠219170917
2024 Richmond 7 games, 230 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31atVirginiaL 13–⁠341439011––
Sep 7vs.WoffordL 19–⁠26124619310
Sep 28atElonW 27–⁠17824011––
Oct 19vs.DelawareW 28–⁠941006––
Oct 26atBryantW 41–⁠141276022––
Nov 2vs.TowsonW 35–⁠242−100––
Nov 23vs.William & MaryW 27–⁠0436021––

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.