Defensive back, Rutgers, 2010–⁠14

Gareef Glashen

Lettered 2011–⁠14 (school media guide)

Number
No. 2
Height
5′10″
Hometown
Miami, FL

Gareef Glashen played defensive back at Rutgers (2010–⁠14).

Team titles: Big East champions, 2012

Defense

SeasonTeamInt
2013Rutgers1
2014Rutgers1
Career2

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

SeasonGSoloAstTklTFLSacksIntPBU
201122021000
201254370000
2013N111724414.5213
On file2327505.5213

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
2010Rutgers2DB
2011Rutgers2DB
2012Rutgers2DB
2013Rutgers2DB
2014Rutgers2DB5′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

2014 Rutgers 1 game with an interception on file, 1 INT
DateOpponentResultInt
Sep 6vs.HowardW 38–⁠251
2013 Rutgers 1 game with an interception on file, 1 INT
DateOpponentResultInt
Dec 7vs.South FloridaW 31–⁠61

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.