Quarterback, UConn, 2007–⁠10

Cody Endres

Number
No. 12
Height
6′4″
Hometown
Washington, PA

Cody Endres played quarterback at UConn (2007–⁠10).

Career highs

378passing yards, best game on fileat West Virginia, 2009

Team titles: Big East champions, 2010

Passing

Passing yards, season by season, with his team’s record
SeasonTeamCmpAttPctYdsY/ATDInt
2008*UConn398446.44114.903
2009UConn9815463.61,3548.864
2010UConn457560.04716.352
On file (2008–⁠10)18231358.12,2367.1119

Rushing

SeasonTeamCarYdsAvgTDLong
2008*UConn2−25−12.500
2009UConn17−97−5.705
2010UConn210.501
On file (2008–⁠10)21−121−5.805

Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.

On the roster

SeasonTeamNo.PosHt
2008UConn12QB
2009UConn12QB
2010UConn12QB6′4″

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.

Game by game

2010 UConn 3 games, 471 passing yards, 5 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 25vs.BuffaloW 45–⁠21711139201
Oct 2vs.VanderbiltW 40–⁠212130179210
Oct 8atRutgersL 24–⁠27173415311–
2009 UConn 7 games, 1,354 passing yards, 6 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 12vs.North CarolinaL 10–⁠12373000−14
Sep 19atBaylorW 30–⁠22122314700−13
Sep 26vs.Rhode IslandW 52–⁠10233028920−21
Oct 10atPittsburghL 21–⁠24172319710−32
Oct 17vs.LouisvilleW 38–⁠25142127311−8
Oct 24atWest VirginiaL 24–⁠28254137823−9
Oct 31vs.RutgersL 24–⁠28494000–
2008 UConn 3 games, 411 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Aug 28vs.HofstraW 35–⁠3454900−18
Oct 25vs.CincinnatiW 40–⁠16184219600−7
Nov 1vs.West VirginiaL 13–⁠35173716603–

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.