Receiver, Army, 2023–⁠26

Samari Howard

Lettered 2024–⁠25 (school media guide)

Number
No. 27
Height
5′8″
Weight
189 lb
Class (2026)
Senior
Hometown
Temple, TX

Samari Howard plays receiver for Army. Last time out, against Florida Atlantic: 5 carries, 43 yards, 1 TD; 1 catch, 2 yards.

2026 so far

347 rushing yards, 2 TD

Last game: 5 carries, 43 yards, 1 TD; 1 catch, 2 yards vs. Florida Atlantic, W 56–⁠24

Next game: at Tulsa, Oct 23

Game by game this season, receiving yards
  1. 52BRY
  2. 10USF
  3. 11@LT
  4. 2FAU

Filled bars: wins; outlined: losses.

Career highs

158rushing yards, career highat Louisiana Tech, 2026

Team titles: American champions, 2024

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2024Army2115.507
2025Army1113312.1141
2026Army8759.4033
Career2121910.4141

Rushing

SeasonTeamCarYdsAvgTDLong
2024Army231285.6021
2025Army13413.2015
2026Army3434710.2254
Career705167.4254

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023Army27WRFr.
2024Army27WRSo.
2025Army27WRJr.
2026Army27WRSr.5′8″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/playPctileMedianTotalUsage
2024Army270.19––5.15%
2025Army280.35––9.74%
2026Army450.4755th (n=829)0.4321.311%

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.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2026Army58%4.102.504.7018%

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 Army 6 games, 347 rushing yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 5vs.BryantW 59–⁠335203363
Sep 12vs.South FloridaL 24–⁠28210093
Sep 25atTempleW 21–⁠17––––69
Oct 3atLouisiana TechL 29–⁠3121108158
Oct 10vs.TulaneW 20–⁠17––––11
Oct 17vs.Florida AtlanticW 56–⁠24120243
2025 Army 9 games, 11 catches, 133 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 6atKansas StateW 24–⁠2131608–
Sep 20vs.North TexasL 38–⁠45221117–
Sep 25atEast CarolinaL 6–⁠282260130
Oct 4atUABW 31–⁠13248041–
Oct 18atTulaneL 17–⁠241808–
Nov 8vs.TempleW 14–⁠13––––4
Nov 22vs.TulsaL 25–⁠26––––15
Nov 29atUTSAW 27–⁠2411401410
Dec 13vs.NavyL 16–⁠17––––12
2024 Army 8 games, 128 rushing yards
DateOpponentResultRecYdsTDLongRush
Aug 30vs.LehighW 42–⁠7170725
Sep 7atFlorida AtlanticW 24–⁠7––––5
Sep 21vs.RiceW 37–⁠14––––22
Sep 26atTempleW 42–⁠14––––10
Oct 5atTulsaW 49–⁠7––––4
Oct 12vs.UABW 44–⁠10––––37
Nov 9atNorth TexasW 14–⁠3––––0
Nov 23vs.Notre DameL 14–⁠49140425

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.