Defensive back, Central Arkansas (from San Diego State), 2013–⁠16

Brandon Porter

Number
No. 18
Height
5′11″
Hometown
Waggaman, LA

Brandon Porter played defensive back at San Diego State (2013–⁠14) and Central Arkansas (2016).

Returns

SeasonTeamKRYdsTD
2013San Diego State2130

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Central Arkansas100010

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
2013N10202
2014E10 of 1321526

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: N, NCAA statistics, via octonion/football, the season’s official lines (G: games played); E, ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2013San Diego State18DB
2014San Diego State18DB
2016Central Arkansas18DB5′11″

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

2016 Central Arkansas 1 game, 1 tackle
DateOpponentResultKRYdsTklSacksPD
Sep 24atArkansas StateW 28–⁠23––101

No box score in the source for Sep 1 vs. Houston Christian; Sep 10 vs. Samford; Sep 17 vs. Northwestern State; Oct 1 at Abilene Christian; Oct 15 at McNeese; Oct 22 vs. Lamar; Oct 29 at SE Louisiana; Nov 5 at Stephen F. Austin; Nov 12 vs. Nicholls; Nov 19 at Sam Houston; Nov 26 vs. Illinois State; Dec 3 at Eastern Washington, so those games are not listed.

2013 San Diego State 2 games, 2 returns, 13 yards
DateOpponentResultKRYdsTklSacksPD
Nov 23vs.Boise StateW 34–⁠3116–––
Dec 21 ✦vs.BuffaloW 49–⁠2417–––

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

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.