Cornerback, South Alabama, 2012–⁠13

Tyrell Pearson

Number
No. 9
Height
5′8″
Hometown
Greenville, SC

Tyrell Pearson played cornerback at South Alabama (2012–⁠13).

Defense

SeasonTeamInt
2012South Alabama4
2013South Alabama2
Career6

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
20121221194034111
2013N776130210
On file28255336121

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
2012South Alabama9CB
2013South Alabama9CB5′8″

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 South Alabama 1 game with an interception on file, 2 INT
DateOpponentResultInt
Sep 14vs.Western KentuckyW 31–⁠242
2012 South Alabama 4 games with an interception on file, 4 INT
DateOpponentResultInt
Sep 1vs.UTSAL 31–⁠331
Sep 22atMississippi StateL 10–⁠301
Nov 10atNorth TexasL 14–⁠241
Dec 1atHawai’iL 7–⁠231

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.