Receiver, Boise State, 2021–26
Ben Ford
- Number
- No. 82
- Height
- 5′10″
- Weight
- 187 lb
- Class (2026)
- Senior
- Hometown
- Eagle, ID
Ben Ford plays receiver for Boise State. Last time out, at Fresno State: 4 catches, 45 yards.
2026 so far
12 catches, 137 yards, 2 TD
Last game: 4 catches, 45 yards at Fresno State, W 38–31
Next game: at Washington State, Oct 24
Filled bars: wins; outlined: losses.
Career highs
6catches, career highvs. New Mexico, 202582receiving yards, career highvs. Eastern Washington, 20252receiving touchdowns, career hightwice; last vs. New Mexico, 2025Team titles: Mountain West champions, 2023, 2024 and 2025
Receiving
* The season in progress, so far.
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2024 | Boise State | 4 | 34 | 8.5 | 0 | 12 |
| 2025 | Boise State | 21 | 325 | 15.5 | 5 | 60 |
| 2026 | Boise State | 12 | 137 | 11.4 | 2 | 31 |
| Career | 37 | 496 | 13.4 | 7 | 60 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Boise State | 82 | WR | RS | ||
| 2023 | Boise State | 82 | WR | Fr. | ||
| 2024 | Boise State | 82 | WR | So. | ||
| 2025 | Boise State | 82 | WR | Jr. | ||
| 2026 | Boise State | 82 | WR | Sr. | 5′10″ | 187 |
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 |
|---|---|---|---|---|---|---|---|
| 2024 | Boise State | 4 | 1.13 | – | – | 4.5 | – |
| 2025 | Boise State | 32 | 1.17 | 99th (n=1040) | 0.46 | 37.4 | 6% |
| 2026 | Boise State | 15 | 0.66 | – | – | 9.9 | – |
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 Boise State 5 games, 12 catches, 137 yards, 2 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 5 | at | L 27–34 | 1 | 8 | 0 | 8 |
| Sep 19 | vs. | W 38–24 | 3 | 29 | 0 | 17 |
| Sep 26 | at | W 32–7 | 1 | 6 | 1 | 6 |
| Oct 3 | vs. | W 37–18 | 3 | 49 | 1 | 31 |
| Oct 10 | at | W 38–31 | 4 | 45 | 0 | 17 |
2025 Boise State 7 games, 21 catches, 325 yards, 5 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 28 | at | L 7–34 | 4 | 44 | 0 | 24 |
| Sep 5 | vs. | W 51–14 | 3 | 82 | 2 | 60 |
| Sep 20 | at | W 49–37 | 1 | 22 | 0 | 22 |
| Sep 27 | vs. | W 47–14 | 3 | 45 | 1 | 18 |
| Oct 4 | at | L 7–28 | 3 | 28 | 0 | 13 |
| Oct 11 | vs. | W 41–25 | 6 | 78 | 2 | 25 |
| Oct 18 | vs. | W 56–31 | 1 | 26 | 0 | 26 |
2024 Boise State 4 games, 4 catches, 34 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 31 | at | W 56–45 | 1 | 9 | 0 | 9 |
| Nov 29 | vs. | W 34–18 | 1 | 8 | 0 | 8 |
| Dec 6 | vs. | W 21–7 | 1 | 5 | 0 | 5 |
| Dec 31 ✦ | vs. | L 14–31 | 1 | 12 | 0 | 12 |
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.
