Running back, Utah Tech, 2024–⁠26

Asa Chatman

Number
No. 0
Height
5′11″
Weight
195 lb
Class (2026)
Junior
Hometown
Lake Elsinore, CA

Asa Chatman plays running back for Utah Tech. Last time out, against Southern Utah: 19 carries, 101 yards, 2 TD; 4 catches, 28 yards, 2 TD. Chatman leads Utah Tech in receiving touchdowns and rushing touchdowns this season.

2026 so far

409 rushing yards, 5 TD

Last game: 19 carries, 101 yards, 2 TD; 4 catches, 28 yards, 2 TD vs. Southern Utah, L 33–⁠46

Next game: at Cal Poly, Oct 24

Game by game this season, rushing yards
  1. 20MTST
  2. 38@BYU
  3. 95@MONT
  4. 110NAU
  5. 45@UNCO
  6. 101SUU

Filled bars: wins; outlined: losses.

Career highs

110rushing yards, career highvs. Northern Arizona, 20262rushing touchdowns, career hightwice; last vs. Southern Utah, 20269catches, career highvs. Southern Utah, 20252receiving touchdowns, career highvs. Southern Utah, 2026

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Utah Tech6366.0020
2025Utah Tech1215364.4566
2026Utah Tech964094.3530
Career2239814.41066

Receiving

SeasonTeamRecYdsAvgTDLong
2024Utah Tech5132.609
2025Utah Tech391774.5018
2026Utah Tech131048.0322
Career572945.2322

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Utah Tech0RBFr.
2025Utah Tech0RBSo.
2026Utah Tech0RBJr.5′11″195

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
2025Utah Tech (FCS)1750.0125th (n=576)0.101.923%
2026Utah Tech (FCS)1170.1049th (n=478)0.1011.530%

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 Utah Tech 6 games, 409 rushing yards, 5 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 29vs.Montana StateL 0–⁠5413200130
Sep 5atBYUL 7–⁠6312381–––
Sep 12atMontanaL 14–⁠35219502110
Sep 19vs.Northern ArizonaL 23–⁠351911014391
Sep 26atNorthern ColoradoL 13–⁠37124512230
Oct 3vs.Southern UtahL 33–⁠461910124282
2025 Utah Tech 11 games, 536 rushing yards, 5 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30vs.UC DavisL 24–⁠3172104190
Sep 6atNorthern ArizonaL 31–⁠3811631520
Sep 13atIdahoL 6–⁠205902190
Sep 20vs.Northern IowaW 20–⁠9129711−30
Sep 27atAustin PeayL 10–⁠42102704170
Oct 4atCentral ArkansasL 17–⁠2315690590
Oct 11vs.Tarleton StateL 23–⁠419240–––
Oct 25vs.Southern UtahL 7–⁠28124109630
Nov 1vs.North AlabamaW 34–⁠331810123170
Nov 8atAbilene ChristianL 10–⁠31134914330
Nov 15atWest GeorgiaL 0–⁠239350210
2024 Utah Tech 3 games, 36 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Oct 19vs.Austin PeayL 7–⁠132802150
Oct 26atEastern KentuckyL 17–⁠284280230
Nov 23atSouthern UtahL 34–⁠37–––1−50

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.