Running back, New Haven (from Pittsburgh), 2023–26
Caleb Williams
- Number
- No. 6
- Height
- 5′9″
- Weight
- 207 lb
- Class (2026)
- Senior
- Hometown
- Pittsburgh, PA
Caleb Williams plays running back for New Haven, after Pittsburgh (2023–25).
2026 so far
16 rushing yards
Last game: at Robert Morris, W 26–15
Next game: at Central Connecticut, Oct 24
Filled bars: wins; outlined: losses.
Rushing
* The season in progress, so far.
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2025 | Pittsburgh | 7 | 10 | 1.4 | 0 | 4 |
| 2026 | New Haven | 8 | 16 | 2.0 | 0 | 5 |
| Career | 15 | 26 | 1.7 | 0 | 5 | |
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2025 | Pittsburgh | 1 | 1 | 0 | 0 | 0 | 0 |
| 2026 | New Haven | 2 | 2 | 0 | 0 | 0 | 0 |
| Career | 3 | 3 | 0 | 0 | 0 | 0 | |
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2025 | Pittsburgh | 2 | −1 | −0.5 | 0 | 0 |
| 2026 | New Haven | 1 | 6 | 6.0 | 0 | 6 |
| Career | 3 | 5 | 1.7 | 0 | 6 | |
Returns
| Season | Team | KR | Yds | TD |
|---|---|---|---|---|
| 2024 | Pittsburgh | 1 | 15 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2023 | Pittsburgh | 6 | RB | Fr. | ||
| 2024 | Pittsburgh | 6 | RB | So. | ||
| 2025 | Pittsburgh | 6 | RB | Jr. | ||
| 2026 | New Haven | 6 | RB | Sr. | 5′9″ | 207 |
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 | Pittsburgh | 9 | -0.74 | – | – | -6.6 | – |
| 2026 | New Haven (FCS) | 9 | -0.37 | – | – | -3.3 | – |
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 New Haven 4 games, 16 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Tkl | Sacks | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 28 | vs. | W 22–21 | 1 | 0 | 0 | 1 | 0 | 0 |
| Sep 12 | at | L 14–57 | 4 | 12 | 0 | 1 | 0 | 0 |
| Sep 19 | vs. | L 10–17 | 2 | 5 | 0 | – | – | – |
| Oct 17 | at | W 26–15 | 1 | −1 | 0 | – | – | – |
2025 Pittsburgh 5 games, 10 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Tkl | Sacks | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | vs. | W 61–9 | 1 | 4 | 0 | – | – | – |
| Oct 4 | vs. | W 48–7 | 2 | 4 | 0 | – | – | – |
| Oct 25 | vs. | W 53–34 | 2 | 1 | 0 | – | – | – |
| Nov 29 | vs. | L 7–38 | – | – | – | 1 | 0 | 0 |
| Dec 27 ✦ | vs. | L 17–23 | 2 | 1 | 0 | – | – | – |
2024 Pittsburgh 1 game, 1 return, 15 yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Tkl | Sacks | PD |
|---|---|---|---|---|---|---|---|---|
| Dec 26 ✦ | vs. | L 46–48 | – | – | – | – | – | – |
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.
