Running back, Tennessee Tech, 2024–⁠26

Aidan Littles

Number
No. 0
Height
5′10″
Weight
205 lb
Class (2026)
Junior
Hometown
Sevierville, TN

Aidan Littles plays running back for Tennessee Tech. Last time out, against Eastern Kentucky: 8 carries, 43 yards; 3 catches, 15 yards.

2026 so far

42 rushing yards

Last game: 8 carries, 43 yards; 3 catches, 15 yards vs. Eastern Kentucky, W 49–⁠20

Next game: at The Citadel, Oct 24

Game by game this season, rushing yards
  1. 6@UTC
  2. -3SAM
  3. -7@WCU
  4. 3FUR
  5. 43EKU

Filled bars: wins; outlined: losses.

Career highs

118rushing yards, career highat Gardner-Webb, 2024

Team titles: Big South–OVC Football Association champions, 2024 and 2025

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Tennessee Tech633896.2387
2025Tennessee Tech472455.2448
2026Tennessee Tech13423.2015
Career1236765.5787

Receiving

SeasonTeamRecYdsAvgTDLong
2024Tennessee Tech9879.7024
2025Tennessee Tech141017.2337
2026Tennessee Tech8475.9015
Career312357.6337

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Tennessee Tech0RBFr.
2025Tennessee Tech0RBSo.
2026Tennessee Tech0RBJr.5′10″205

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
2025Tennessee Tech (FCS)580.14––7.98%
2026Tennessee Tech (FCS)21-0.12––-2.57%

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 Tennessee Tech 6 games, 42 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 29vs.MonmouthW 38–⁠14––––––
Sep 5atChattanoogaW 24–⁠9160–––
Sep 12vs.SamfordW 45–⁠191−30–––
Oct 3atWestern CarolinaL 20–⁠442−70–––
Oct 10vs.FurmanW 20–⁠151305320
Oct 17vs.Eastern KentuckyW 49–⁠2084303150
2025 Tennessee Tech 12 games, 245 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30vs.Cumberland (TN)W 65–⁠011501111
Sep 6vs.ChattanoogaW 45–⁠1777211371
Sep 13vs.DavidsonW 72–⁠14260–––
Sep 27atTennessee StateW 35–⁠89191–––
Oct 4vs.Western IllinoisW 66–⁠2052211−30
Oct 11atCharleston SouthernW 27–⁠135491–––
Oct 18atLindenwoodW 52–⁠28120150
Oct 25vs.Southeast Missouri StateW 42–⁠2353301141
Nov 1vs.Gardner-WebbW 27–⁠21230140
Nov 8atEastern IllinoisW 21–⁠931303130
Nov 15atKentuckyL 10–⁠42460–––
Nov 29vs.North DakotaL 6–⁠313505200
2024 Tennessee Tech 9 games, 389 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 7atGeorgiaL 3–⁠486450–––
Sep 28atGardner-WebbW 52–⁠21101181–––
Oct 5vs.South Carolina StateL 20–⁠2241701240
Oct 12atSoutheast Missouri StateL 3–⁠345004250
Oct 19atWestern IllinoisL 21–⁠3721501110
Oct 26vs.Charleston SouthernW 28–⁠238410–––
Nov 2vs.LindenwoodW 52–⁠1011981–––
Nov 9atSamfordW 27–⁠79371150
Nov 16atUT MartinW 10–⁠981802220

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.