Quarterback, Army, 2022–⁠25

Dewayne Coleman

Lettered 2024–⁠25 (school media guide)

Number
No. 10
Height
5′10″
Weight
200 lb
Class (2025)
Senior
Hometown
Selma, TX

Dewayne Coleman played quarterback at Army (2022–⁠25).

Career highs

117rushing yards, career highvs. North Texas, 2025

Team titles: American champions, 2024

Passing

Passing yards, season by season, with his team’s record
SeasonTeamCmpAttPctYdsY/ATDInt
2023Army11100.0−14−14.000
2024Army111668.81217.610
2025Army193652.82737.622
Career315358.53807.232

Rushing

SeasonTeamCarYdsAvgTDLong
2023Army482.005
2024Army381363.6115
2025Army852973.5326
Career1274413.5426

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Army10QBFr.
2023Army10QBSo.
2024Army10QBJr.
2025Army10QBSr.5′10″200

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
2023Army4-0.18––-0.7––
2024Army520.17––9.014%0.14
2025Army1200.15––18.029%0.10

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.

Passing detail

SeasonTeamSuccessDepthAfter catchDeep throwsDeep completed
2025Army27%16.0 yds–0 of 1–

Success: passes that kept the offense on schedule. Depth: how far downfield his passes traveled in the air, on average. After catch: yards his receivers gained after the catch, per completion. Deep throws: the play-by-play gives depth and direction for about half of a passer’s throws; this is how many of those went deep, and how many of the deep ones were caught. From CollegeFootballData, FBS games, 2025 on.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2025Army46%2.800.800.3018%

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

2025 Army 6 games, 297 rushing yards, 3 TD
DateOpponentResultCmpAttYdsTDIntRush
Aug 29vs.Tarleton StateL 27–⁠3071212902100
Sep 20vs.North TexasL 38–⁠4561110120117
Sep 25atEast CarolinaL 6–⁠2859360051
Oct 4atUABW 31–⁠13117006
Oct 11vs.CharlotteW 24–⁠70200022
Dec 27 ✦vs.UConnW 41–⁠16010001
2024 Army 6 games, 136 rushing yards, 1 TD
DateOpponentResultCmpAttYdsTDIntRush
Aug 30vs.LehighW 42–⁠72222006
Sep 21vs.RiceW 37–⁠1423130024
Sep 26atTempleW 42–⁠1411181017
Oct 5atTulsaW 49–⁠711200021
Oct 12vs.UABW 44–⁠100100026
Nov 2vs.Air ForceW 20–⁠358480042
2023 Army 2 games, −14 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Sep 2atUL MonroeL 13–⁠1711−14001
Oct 21atLSUL 0–⁠62–––––7

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.