Defensive tackle, Colorado, 2012–⁠16

Samson Kafovalu

Number
No. 54
Height
6′4″
Hometown
Riverside, CA

Samson Kafovalu played defensive tackle at Colorado (2012–⁠16).

Career highs

9tackles, career highvs. Oklahoma State, 2016

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Colorado53294203

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTklTFLSacks
20127861400
2013N669155.53
2015E9 of 135813––

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); 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
2012Colorado54DT
2013Colorado54DT
2014Colorado54DT
2015Colorado54DT
2016Colorado54DT6′4″

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 Colorado 14 games, 53 tackles, 2 sacks
DateOpponentResultTklSoloTFLSacksPD
Sep 2vs.Colorado StateW 44–⁠733000
Sep 10vs.Idaho StateW 56–⁠710000
Sep 17atMichiganL 28–⁠4563110
Sep 24atOregonW 41–⁠3875110
Oct 1vs.Oregon StateW 47–⁠620000
Oct 8atUSCL 17–⁠2140000
Oct 15vs.Arizona StateW 40–⁠1621000
Oct 22atStanfordW 10–⁠521000
Nov 3vs.UCLAW 20–⁠1043000
Nov 12atArizonaW 49–⁠2421000
Nov 19vs.Washington StateW 38–⁠2466000
Nov 26vs.UtahW 27–⁠2221000
Dec 2vs.WashingtonL 10–⁠4131000
Dec 29 ✦vs.Oklahoma StateL 8–⁠3894200

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.