Running back, Alabama A&M, 2022–⁠25

Ryan Morrow

Number
No. 26
Height
5′11″
Weight
213 lb
Class (2025)
Sophomore
Hometown
Maplesville, AL

Ryan Morrow played running back at Alabama A&M (2022–⁠25).

Career highs

136rushing yards, career highvs. Florida A&M, 2025

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2023Alabama A&M651892.9217
2024Alabama A&M492966.0165
2025Alabama A&M1074404.1380
Career2219254.2680

Receiving

SeasonTeamRecYdsAvgTDLong
2022Alabama A&M144.004
2023Alabama A&M6264.308
2024Alabama A&M6589.7118
2025Alabama A&M6416.8018
Career191296.8118

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Alabama A&M26RBYr 1
2023Alabama A&M26RBYr 2
2024Alabama A&M26RBYr 3
2025Alabama A&M26RBSo. (Yr 4)5′11″213

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
2022Alabama A&M (FCS)1-0.17––-0.2–
2023Alabama A&M (FCS)66-0.102nd (n=450)0.17-6.412%
2024Alabama A&M (FCS)490.34––16.99%
2025Alabama A&M (FCS)110-0.115th (n=576)0.10-11.915%

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 Alabama A&M 12 games, 440 rushing yards, 3 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30atArkansasL 7–⁠523−800118
Sep 6vs.Alcorn StateW 41–⁠314250101−5
Sep 13atTennessee StateW 23–⁠2131506––
Sep 20vs.Lane CollegeW 49–⁠7103311215
Sep 27atBethune-CookmanL 34–⁠41926012––
Oct 4vs.Jackson StateL 24–⁠57122905111
Oct 11vs.Mississippi Valley StateW 45–⁠25952115––
Oct 25vs.Alabama StateL 13–⁠5671808––
Nov 1atGramblingL 10–⁠131141012––
Nov 8vs.Prairie View A&ML 5–⁠4812905––
Nov 15vs.Florida A&ML 23–⁠2618136180––
Nov 22atTexas SouthernL 7–⁠24964032212
2024 Alabama A&M 8 games, 296 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31atAuburnL 3–⁠735180101−4
Sep 7vs.Kentucky StateW 49–⁠7869031118
Sep 14vs.Georgetown College KentuckyW 24–⁠16773020224
Sep 21atAustin PeayL 16–⁠5961305––
Oct 5vs.Jackson StateL 38–⁠4581409112
Oct 12vs.Bethune-CookmanW 56–⁠121083165––
Oct 26vs.Alabama StateL 19–⁠272403––
Nov 2vs.SouthernL 20–⁠2532201718
2023 Alabama A&M 8 games, 189 rushing yards, 2 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 2atVanderbiltL 13–⁠4752601226
Sep 21vs.Arkansas–Pine BluffW 31–⁠241439017214
Oct 7vs.Jackson StateL 30–⁠4582401114
Oct 14atGramblingW 45–⁠241039111––
Oct 28vs.Alabama StateL 16–⁠3151201112
Nov 4vs.Florida A&ML 28–⁠426618––
Nov 11atBethune-CookmanL 14–⁠31832013––
Nov 16vs.Mississippi Valley StateW 30–⁠2191104––

No box score in the source for Sep 9 vs. Lane College; Sep 16 at Southern; Sep 30 vs. Tuskegee, so those games are not listed.

2022 Alabama A&M 1 game, 1 return, 9 yards
DateOpponentResultCarYdsTDLongRecRec yds
Nov 19vs.Texas SouthernW 24–⁠20––––14

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.