Running back, South Carolina (from South Carolina State), 2023–⁠26

Jawarn Howell

Lettered 2025 (school media guide)

Number
No. 22
Height
6′1″
Weight
222 lb
Class (2026)
Junior
Hometown
Mooresville, NC

Jawarn Howell plays running back for South Carolina, after South Carolina State (2023).

2026 so far

104 rushing yards

Last game: at Florida, W 38–⁠19

Next game: vs. Tennessee, Oct 24

Game by game this season, rushing yards
  1. 62KENT
  2. 30TOW
  3. 6@ALA
  4. 6@FLA

Filled bars: wins; outlined: losses.

Career highs

283rushing yards, career highvs. Howard, 20233rushing touchdowns, career hightwice; last vs. Howard, 202393receiving yards, career highvs. Tennessee Tech, 2023

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2023South Carolina State1028097.9785
2024South Carolina191236.5227
2025South Carolina14805.7014
2026South Carolina181045.8016
Career1531,1167.3985

Receiving

SeasonTeamRecYdsAvgTDLong
2023South Carolina State1014914.9290
2024South Carolina155.005
2025South Carolina46115.3036
Career1521514.3290

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023South Carolina State22RBYr 1
2024South Carolina22RBYr 2
2025South Carolina22RBYr 3
2026South Carolina22RBJr. (Yr 4)6′1″222

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
2023South Carolina State (FCS)560.22––12.119%
2024South Carolina210.28––5.86%
2025South Carolina180.61––10.9–
2026South Carolina170.19––3.2–

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 South Carolina 4 games, 104 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5vs.Kent StateW 57–⁠0962016––
Sep 12vs.TowsonW 45–⁠9430010––
Sep 26atAlabamaL 18–⁠491606––
Oct 10atFloridaW 38–⁠194605––
2025 South Carolina 4 games, 80 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 6vs.South Carolina StateW 38–⁠1073009––
Nov 15atTexas A&ML 30–⁠3133001419
Nov 22vs.Coastal CarolinaW 51–⁠731809252
Nov 29vs.ClemsonL 14–⁠28120210
2024 South Carolina 5 games, 123 rushing yards, 2 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 21vs.AkronW 50–⁠7533123––
Oct 5vs.Ole MissL 3–⁠2741908––
Oct 19atOklahomaW 35–⁠93503––
Nov 23vs.WoffordW 56–⁠12235127––
Dec 31 ✦vs.IllinoisL 17–⁠2153101515
2023 South Carolina State 9 games, 809 rushing yards, 7 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 26vs.Jackson StateL 7–⁠37134809110
Sep 2atCharlotteL 3–⁠2413330810
Sep 9atGeorgia TechL 13–⁠48664047––
Sep 23vs.The CitadelW 31–⁠10626012419
Oct 7vs.Virginia LynchburgW 56–⁠6676028127
Oct 14vs.Tennessee TechL 7–⁠28934024393
Oct 21atDelaware StateW 35–⁠713119334––
Oct 26atNorth Carolina CentralL 28–⁠629126151––
Nov 4vs.HowardW 27–⁠2427283385––

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.