Quarterback, UCLA (from Pittsburgh, Cal Poly), 2023–26
Ty Dieffenbach
- Number
- No. 14
- Height
- 6′6″
- Weight
- 227 lb
- Class (2026)
- Junior
- Hometown
- Calabasas, CA
Ty Dieffenbach plays quarterback for UCLA, after Pittsburgh (2023–24) and Cal Poly (2025). Last time out, against Wisconsin: 22 of 33, 264 yards, 1 INT; 6 carries, −12 yards, a career high in passing yards.
2026 so far
307 passing yards, 1 TD
Last game: 22 of 33, 264 yards ★, 1 INT; 6 carries, −12 yards vs. Wisconsin, W 17–7
Next game: vs. Michigan State, Oct 24
Filled bars: wins; outlined: losses.
Career highs
264passing yards, career highvs. Wisconsin, 20263touchdown passes, career highvs. Western Oregon, 2025142rushing yards, career highat Idaho State, 20252rushing touchdowns, career highvs. Portland State, 2025Passing
* The season in progress, so far.
Rushing
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2023 | Pittsburgh | 14 | QB | RS | ||
| 2024 | Pittsburgh | 14 | QB | Fr. | ||
| 2025 | Cal Poly | 14 | QB | So. | ||
| 2026 | UCLA | 14 | QB | Jr. | 6′6″ | 227 |
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 | Cal Poly (FCS) | 225 | 0.34 | 77th (n=314) | 0.24 | 76.7 | 39% |
| 2026 | UCLA | 49 | 0.16 | – | – | 7.7 | 34% |
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.
Passing detail
| Season | Team | Success | Depth | After catch | Deep throws | Deep completed |
|---|---|---|---|---|---|---|
| 2026 | UCLA | 49% | 9.3 yds | 6.1 yds | 7 of 38 | 43% |
Success: passes that kept the offense on schedule. Depth: how far downfield his passes traveled in the air, on average. After catch: yards his receivers gained after the catch, per completion. Deep throws: the play-by-play gives depth and direction for about half of a passer’s throws; this is how many of those went deep, and how many of the deep ones were caught. From CollegeFootballData, FBS games, 2025 on.
Game by game
2026 UCLA 2 games, 307 passing yards, 1 TD
2025 Cal Poly 9 games, 1,305 passing yards, 9 TD
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | at | W 41–17 | 18 | 27 | 263 | 2 | 0 | 69 |
| Sep 6 | at | L 9–63 | 6 | 9 | 82 | 0 | 1 | −7 |
| Sep 13 | vs.Western Oregon | W 56–7 | 8 | 11 | 192 | 3 | 0 | 13 |
| Sep 20 | at | L 17–35 | 1 | 2 | 42 | 0 | 0 | 14 |
| Oct 11 | at | L 9–28 | 15 | 33 | 225 | 1 | 4 | 13 |
| Oct 25 | vs. | L 17–34 | 2 | 5 | 3 | 0 | 0 | 9 |
| Nov 1 | vs. | L 35–40 | 14 | 23 | 207 | 1 | 1 | 64 |
| Nov 8 | at | L 17–27 | 18 | 29 | 172 | 1 | 1 | 142 |
| Nov 15 | at | L 27–35 | 10 | 23 | 119 | 1 | 2 | 4 |
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.
