Defensive back, Vanderbilt, 2009–⁠12

Eddie Foster

Number
No. 16
Height
5′10″
Hometown
Colleyville, TX

Eddie Foster played defensive back at Vanderbilt (2009–⁠12).

Defense

SeasonTeamInt
2009Vanderbilt2
2010Vanderbilt1
2011Vanderbilt1
Career4

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

SeasonGSoloAstTklTFLSacksIntPBUFFHur
2009911617112100
201012361753601312
20115617001100
2012813215000100
On file662692714612

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2009Vanderbilt16DB
2010Vanderbilt16DB
2011Vanderbilt16DB
2012Vanderbilt16DB5′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

2011 Vanderbilt 1 game with an interception on file, 1 INT
DateOpponentResultInt
Sep 17vs.Ole MissW 30–⁠71
2010 Vanderbilt 1 game with an interception on file, 1 INT
DateOpponentResultInt
Sep 18atOle MissW 28–⁠141
2009 Vanderbilt 2 games with an interception on file, 2 INT
DateOpponentResultInt
Sep 26atRiceW 36–⁠171
Nov 14vs.KentuckyL 13–⁠241

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.