Running back, East Carolina, 2024–⁠26

T.J. Engleman

Number
No. 4
Height
5′9″
Weight
189 lb
Class (2026)
Junior
Hometown
Atlanta, GA

T.J. Engleman plays running back for East Carolina. Last time out, at UAB: 26 carries, 104 yards; 3 catches, 17 yards. Engleman leads East Carolina in rushing touchdowns and rushing yards this season.

2026 so far

490 rushing yards, 3 TD

Last game: 26 carries, 104 yards; 3 catches, 17 yards at UAB, L 17–⁠30

Next game: at Memphis, Oct 22

Game by game this season, rushing yards
  1. -2@ALA
  2. 24APP
  3. 99@ODU
  4. 129NCCU
  5. 136RICE
  6. 104@UAB

Filled bars: wins; outlined: losses.

Career highs

136rushing yards, career highvs. Rice, 20262rushing touchdowns, career highvs. North Carolina Central, 2026

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2025East Carolina593065.2123
2026East Carolina714906.9388
Career1307966.1488

Receiving

SeasonTeamRecYdsAvgTDLong
2025East Carolina7375.3020
2026East Carolina7608.6125
Career14976.9125

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024East Carolina4RBFr.
2025East Carolina4RBSo.
2026East Carolina4RBJr.5′9″189

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
2025East Carolina650.1358th (n=576)0.108.49%0.15
2026East Carolina800.3996th (n=478)0.1031.320%0.25

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
2025East Carolina56%3.701.000.3013%
2026East Carolina48%3.401.002.8011%

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 East Carolina 6 games, 490 rushing yards, 3 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5atAlabamaL 10–⁠481−200––
Sep 12vs.App StateL 24–⁠2742408––
Sep 19atOld DominionW 20–⁠171699040––
Sep 26vs.North Carolina CentralW 42–⁠910129288233
Oct 10vs.RiceW 28–⁠1214136143210
Oct 15atUABL 17–⁠3026104012317
2025 East Carolina 9 games, 306 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 6vs.CampbellW 56–⁠35360181−2
Sep 13atCoastal CarolinaW 38–⁠0631112––
Sep 20vs.BYUL 13–⁠341606––
Oct 9atTulaneL 19–⁠26104008420
Oct 16vs.TulsaW 41–⁠271040011219
Nov 1atTempleW 45–⁠14877023––
Nov 8vs.CharlotteW 48–⁠22835014––
Nov 22atUTSAL 24–⁠5851706––
Dec 27 ✦vs.PittsburghW 23–⁠1762408––

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.