Linebacker, Tulane, 2006–⁠09

Travis Burks

Number
No. 6
Height
6′0″
Hometown
Ellenwood, GA

Travis Burks played linebacker at Tulane (2006–⁠09).

Defense

SeasonTeamInt
2008*Tulane2

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. 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

SeasonGSoloAstTklTFLSacksIntFFHur
2006N1262800–––
2007N111642010–––
2008111818363.51211
2009124246882.50001
On file827015271–––

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
2008Tulane6LB
2009Tulane6LB6′0″

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

2009 Tulane 0 games with an interception on file, 1 return, 21 yards
DateOpponentResultInt
2008 Tulane 2 games with an interception on file, 2 INT
DateOpponentResultInt
Nov 1atLSUL 10–⁠351
Nov 8atHoustonL 14–⁠421

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.