Defensive back, Houston, 2009–⁠13

Thomas Bates

Number
No. 13
Height
5′10″
Hometown
Baytown, TX

Thomas Bates played defensive back at Houston (2009–⁠13).

Defense

SeasonTeamInt
2011Houston3
2013Houston2
Career5

Season lines from CollegeFootballData, regular season and bowls. Before 2016 our source records only interceptions for most defenders (no tackles, tackles for loss or sacks), so these lines count interceptions only. His tackles, tackles for loss and sacks from other sources are under “Defense before 2016” below.

Defense before 2016

SeasonGSoloAstTklTFLSacksIntPBUFF
2010452700000
20111022143611370
201210211435100100
2013N1338165410292
On file8646132315262

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2009Houston13DB
2010Houston13DB
2011Houston13DB
2012Houston13DB
2013Houston13DB5′10″

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

2013 Houston 1 game with an interception on file, 2 INT
DateOpponentResultInt
Oct 19vs.BYUL 46–⁠472
2011 Houston 2 games with an interception on file, 3 INT
DateOpponentResultInt
Sep 17atLouisiana TechW 35–⁠342
Oct 8vs.East CarolinaW 56–⁠31

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file. Before 2016 our source’s box scores record only interceptions for defenders (no tackles, tackles for loss or sacks), so only those games are listed. His tackles, tackles for loss and sacks from other sources are under “Defense before 2016” below.

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.