Defensive back, Temple, 2010–⁠14

Anthony Robey

Number
No. 12
Height
5′10″
Hometown
Norristown, PA

Anthony Robey played defensive back at Temple (2010–⁠14).

Defense

SeasonTeamInt
2011Temple1

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
2011N91421621132
2012112417413.51.5060
2013N1237124920030
On file75311067.52.51122

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
2010Temple12DB
2011Temple12DB
2012Temple12DB
2013Temple12DB
2014Temple12DB5′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

2012 Temple 0 games with an interception on file, 2 returns, −11 yards
DateOpponentResultInt
2011 Temple 1 game with an interception on file, 1 INT
DateOpponentResultInt
Dec 17 ✦vs.WyomingW 37–⁠151

No box score in the source for Nov 25 vs. Kent State, so that game is not listed.

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.