Running back, Western Carolina, 2025–26
Josh Perry
- Number
- No. 3
- Height
- 6′0″
- Weight
- 205 lb
- Class (2026)
- Sophomore
- Hometown
- Orlando, FL
Josh Perry plays running back for Western Carolina. Last time out, at Mercer: 12 carries, 50 yards; 3 catches, 28 yards. Perry leads Western Carolina in rushing touchdowns and rushing yards this season.
2026 so far
455 rushing yards, 5 TD
Last game: 12 carries, 50 yards; 3 catches, 28 yards at Mercer, L 14–17
Next game: vs. Chattanooga, Oct 24
Filled bars: wins; outlined: losses.
Career highs
157rushing yards, career highvs. Tennessee Tech, 20263rushing touchdowns, career highvs. Presbyterian, 20266catches, career highvs. Eastern Kentucky, 20262receiving touchdowns, career highvs. Eastern Kentucky, 2026Rushing
* The season in progress, so far.
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2025 | Western Carolina | 10 | 39 | 3.9 | 0 | 7 |
| 2026 | Western Carolina | 92 | 455 | 4.9 | 5 | 62 |
| Career | 102 | 494 | 4.8 | 5 | 62 | |
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2025 | Western Carolina | 2 | 7 | 3.5 | 1 | 9 |
| 2026 | Western Carolina | 18 | 120 | 6.7 | 2 | 23 |
| Career | 20 | 127 | 6.3 | 3 | 23 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2025 | Western Carolina | 3 | RB | Fr. | ||
| 2026 | Western Carolina | 3 | RB | So. | 6′0″ | 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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2025 | Western Carolina (FCS) | 13 | -0.02 | – | – | -0.3 | – |
| 2026 | Western Carolina (FCS) | 115 | 0.14 | 57th (n=478) | 0.10 | 15.6 | 22% |
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 Western Carolina 7 games, 455 rushing yards, 5 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | vs. Eastern Kentucky | W 45–21 | 16 | 31 | 0 | 6 | 29 | 2 |
| Sep 6 | at Campbell | L 19–28 | 4 | 1 | 0 | – | – | – |
| Sep 12 | at Cincinnati | L 10–62 | 7 | 24 | 0 | 2 | 11 | 0 |
| Sep 19 | vs. Presbyterian | W 58–14 | 16 | 142 | 3 | 3 | 20 | 0 |
| Sep 26 | at East Tennessee State | L 31–58 | 12 | 50 | 0 | 1 | 8 | 0 |
| Oct 3 | vs. Tennessee Tech | W 44–20 | 25 | 157 | 2 | 3 | 24 | 0 |
| Oct 10 | at Mercer | L 14–17 | 12 | 50 | 0 | 3 | 28 | 0 |
2025 Western Carolina 2 games, 39 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Oct 11 | vs. Furman | W 52–7 | 9 | 38 | 0 | 1 | 9 | 1 |
| Oct 18 | at The Citadel | W 45–38 | 1 | 1 | 0 | 1 | −2 | 0 |
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.