Safety, TCU, 2010–⁠13

Elisha Olabode

Number
No. 6
Height
5′11″
Hometown
Cedar Hill, TX

Elisha Olabode played safety at TCU (2010–⁠13).

Team titles: Mountain West champions, 2010 and 2011

Defense

SeasonTeamInt
2012TCU4
2013TCU1
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

SeasonGSoloAstTklTFLIntPBUFF
2010N115380–––
20111196150020
2012134823713492
2013N103621572181
On file98531515–––

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
2010TCU6S
2011TCU6S
2012TCU6S
2013TCU6S5′11″

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 TCU 1 game with an interception on file, 1 INT
DateOpponentResultInt
Oct 19atOklahoma StateL 10–⁠241
2012 TCU 4 games with an interception on file, 4 INT
DateOpponentResultInt
Sep 8vs.GramblingW 56–⁠01
Sep 29atSMUW 24–⁠161
Oct 27atOklahoma StateL 14–⁠361
Nov 22atTexasW 20–⁠131

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.