Defensive back, Colorado, 2007–⁠11

Anthony Perkins

Number
No. 7
Height
5′10″
Hometown
Northglenn, CO

Anthony Perkins played defensive back at Colorado (2007–⁠11).

Defense

SeasonTeamInt
2009Colorado2
2010Colorado1
On file (2009–⁠10)3

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
2008N1222133500––1
20091151267711211
201051913321.50110
2011935185310010
On file127701973.51––2

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
2009Colorado7DB
2010Colorado7DB
2011Colorado7DB5′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

2010 Colorado 1 game with an interception on file, 1 INT
DateOpponentResultInt
Sep 4vs.Colorado StateW 24–⁠31
2009 Colorado 2 games with an interception on file, 2 INT
DateOpponentResultInt
Nov 7vs.Texas A&MW 35–⁠341
Nov 19atOklahoma StateL 28–⁠311

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.