Running back, James Madison, 2022–23
Latrele Palmer
- Number
- No. 5
- Height
- 6′0″
- Weight
- 220 lb
- Class (2023)
- Senior
- Hometown
- Boyds, MD
Latrele Palmer played running back at James Madison (2022–23).
Career highs
106rushing yards, career highvs. Texas State, 20223rushing touchdowns, career highvs. Texas State, 2022Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2022 | James Madison | 101 | 404 | 4.0 | 5 | 34 |
| 2023 | James Madison | 32 | 119 | 3.7 | 1 | 13 |
| Career | 133 | 523 | 3.9 | 6 | 34 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | James Madison | 5 | RB | Jr. | ||
| 2023 | James Madison | 5 | RB | Sr. | 6′0″ | 220 |
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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage | Adj. rush |
|---|---|---|---|---|---|---|---|---|
| 2022 | James Madison | 105 | -0.07 | 4th (n=470) | 0.14 | -7.4 | 13% | -0.02 |
| 2023 | James Madison | 34 | -0.03 | – | – | -0.9 | 7% | – |
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.
Game by game
2023 James Madison 8 games, 119 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 2 | vs. Bucknell | W 38–3 | 10 | 45 | 1 | 13 | – | – |
| Sep 9 | at Virginia | W 36–35 | 6 | 30 | 0 | 9 | – | – |
| Sep 16 | at Troy | W 16–14 | 2 | −1 | 0 | 1 | 2 | 26 |
| Sep 23 | at Utah State | W 45–38 | 5 | 15 | 0 | 7 | – | – |
| Sep 30 | vs. South Alabama | W 31–23 | 2 | 3 | 0 | 3 | – | – |
| Nov 4 | at Georgia State | W 42–14 | 2 | 5 | 0 | 3 | 1 | 3 |
| Nov 18 | vs. App State | L 23–26 | 2 | 2 | 0 | 4 | – | – |
| Dec 23 ✦ | vs. Air Force | L 21–31 | 3 | 20 | 0 | 12 | – | – |
2022 James Madison 11 games, 404 rushing yards, 5 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. Middle Tennessee | W 44–7 | 10 | 36 | 0 | 13 | – | – |
| Sep 10 | vs. Norfolk State | W 63–7 | 7 | 25 | 1 | 12 | – | – |
| Sep 24 | atApp State | W 32–28 | 7 | 39 | 0 | 20 | 1 | 5 |
| Oct 1 | vs. Texas State | W 40–13 | 27 | 106 | 3 | 25 | 2 | 24 |
| Oct 8 | at Arkansas State | W 42–20 | 13 | 34 | 0 | 6 | – | – |
| Oct 15 | at Georgia Southern | L 38–45 | 10 | 57 | 0 | 21 | 1 | 8 |
| Oct 22 | vs. Marshall | L 12–26 | 4 | 10 | 0 | 4 | – | – |
| Nov 5 | at Louisville | L 10–34 | 5 | 7 | 0 | 3 | – | – |
| Nov 12 | at Old Dominion | W 37–3 | 4 | 24 | 0 | 10 | – | – |
| Nov 19 | vs.Georgia State | W 42–40 | 6 | 5 | 0 | 3 | 1 | 5 |
| Nov 26 | vs. Coastal Carolina | W 47–7 | 8 | 61 | 1 | 34 | – | – |
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.