Running back, Virginia (from UAB), 2024–⁠26

Solomon Beebe

Number
No. 28
Height
5′10″
Weight
199 lb
Class (2026)
Junior
Hometown
Montgomery, AL

Solomon Beebe plays running back for Virginia, after UAB (2024–⁠25). Last time out, against Syracuse: 1 catch, −3 yards.

2026 so far

1 catch, −3 yards

Last game: 1 catch, −3 yards vs. Syracuse, W 28–⁠25

Next game: vs. Duke, Oct 23

Career highs

106rushing yards, career highvs. Memphis, 20252rushing touchdowns, career hightwice; last at Florida Atlantic, 20256catches, career hightwice; last at Florida Atlantic, 2025

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2024UAB22813.7116
2025UAB563386.0681
Career784195.4781

Returns

SeasonTeamKRYdsTD
2024UAB113160
2025UAB225541
Career338701

Receiving

SeasonTeamRecYdsAvgTDLong
2024UAB2126.007
2025UAB312849.2043
2026Virginia1−3−3.000
Career342938.6043

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024UAB28RBFr.
2025UAB28RBSo.
2026Virginia28RBJr.5′10″199

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
2024UAB23-0.16––-3.64%–
2025UAB880.3196th (n=576)0.1026.911%0.26
2026Virginia1-0.61––-0.6––

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.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2025UAB44%3.801.403.5016%

Where his yards came from, per carry: line yards are the ones credited to the blockers (the first few, and losses), second level the yards 5 to 10 past the line, open field those beyond 10. Success: carries that kept the offense on schedule. Stuffed: carries stopped at or behind the line. From CollegeFootballData, FBS games, 2025 on.

Game by game

2026 Virginia 1 game, 1 catch, −3 yards
DateOpponentResultCarRush ydsRush TDKRYds
Oct 10vs.SyracuseW 28–⁠25–––––
2025 UAB 12 games, 338 rushing yards, 6 TD
DateOpponentResultCarRush ydsRush TDKRYds
Aug 28vs.Alabama StateW 52–⁠4285125110
Sep 6atNavyL 24–⁠386130239
Sep 13vs.AkronW 31–⁠284805154
Sep 20atTennesseeL 24–⁠56140114
Oct 4vs.ArmyL 13–⁠31–––489
Oct 11atFlorida AtlanticL 33–⁠534342122
Oct 18vs.MemphisW 31–⁠2451061––
Nov 1atUConnL 19–⁠386330––
Nov 8atRiceL 17–⁠242120––
Nov 15vs.North TexasL 24–⁠533160235
Nov 22vs.South FloridaL 18–⁠489301291
Nov 29atTulsaW 31–⁠248310––
2024 UAB 9 games, 81 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDKRYds
Aug 29vs.Alcorn StateW 41–⁠37390––
Sep 28vs.NavyL 18–⁠41–––124
Oct 5vs.TulaneL 20–⁠71381350
Oct 12atArmyL 10–⁠441150243
Nov 2vs.TulsaW 59–⁠213100––
Nov 9vs.UConnL 23–⁠31130––
Nov 16atMemphisL 18–⁠53–––––
Nov 23vs.RiceW 40–⁠145−20190
Nov 30atCharlotteL 27–⁠292804109

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.