Quarterback, UAB, 2007–⁠11

Bryan Ellis

Number
No. 10
Height
6′2″
Hometown
Byron, GA

Bryan Ellis played quarterback at UAB (2007–⁠11).

At a glance

Best season
2,940
Passing yards, 2010 (UAB, 4–⁠8)
Best game
418 yards
Vs. East Carolina, week 11, 2010: No. 1 passing game in FBS that week

Career highs

418passing yards, best game on filevs. East Carolina, 20105touchdown passes, best game on filevs. East Carolina, 2010

Passing

Passing yards, season by season, with his team’s record
SeasonTeamCmpAttPctYdsY/ATDInt
2009UAB1425.0143.500
2010UAB23141156.22,9407.22512
2011UAB6712752.87435.925
On file (2009–⁠11)29954255.23,6976.82717

Rushing

SeasonTeamCarYdsAvgTDLong
2010UAB25291.2227
2011UAB11111.0013
On file (2009–⁠11)36401.1227

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009UAB10QB
2010UAB10QB
2011UAB10QB6′2″

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

2011 UAB 4 games, 743 passing yards, 2 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 10atFloridaL 0–⁠3915281410013
Sep 17vs.TulaneL 10–⁠491025145022
Sep 24atEast CarolinaL 23–⁠28223217701−3
Oct 15atTulsaL 20–⁠37204228022−1
2010 UAB 11 games, 2,940 passing yards, 25 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 11atSMUL 7–⁠286114400–
Sep 18vs.TroyW 34–⁠33233736032−4
Sep 25atTennesseeL 29–⁠322955373112
Oct 6atUCFL 7–⁠42143014912−6
Oct 16vs.UTEPW 21–⁠6202827230−5
Oct 23atMississippi StateL 24–⁠292345236105
Oct 30atSouthern MissW 50–⁠492234241336
Nov 6vs.MarshallL 17–⁠312145238212
Nov 11vs.East CarolinaL 42–⁠54314941851−2
Nov 20vs.MemphisW 31–⁠152138361322
Nov 27atRiceL 23–⁠2821392483029
2009 UAB 1 game, 14 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Sep 26atTexas A&ML 19–⁠56141400–

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.