Safety, Bethune-Cookman (from Louisville), 2017–⁠22

TreSean Smith

Number
No. 4
Height
6′1″
Weight
210 lb
Class (2022)
Senior
Hometown
Hamilton, OH

TreSean Smith played safety at Louisville (2017–⁠19) and Bethune-Cookman (2022).

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2017Louisville342041210
2018Louisville281800010
Career623841220

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

On the roster

SeasonTeamNo.PosClassHtWt
2017Louisville4SYr 1
2018Louisville4SYr 2
2019Louisville4SYr 3
2022Bethune-Cookman4SSr. (Yr 6)6′1″210

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

2018 Louisville 10 games, 28 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Sep 8vs.Indiana StateW 31–⁠7320000
Sep 15vs.Western KentuckyW 20–⁠17630001
Sep 22atVirginiaL 3–⁠27330000
Sep 29vs.Florida StateL 24–⁠28220000
Oct 5vs.Georgia TechL 31–⁠66220000
Oct 13atBoston CollegeL 20–⁠38200000
Oct 27vs.Wake ForestL 35–⁠56210000
Nov 3atClemsonL 16–⁠77210000
Nov 17vs.NC StateL 10–⁠52100000
Nov 24vs.KentuckyL 10–⁠56540000
2017 Louisville 13 games, 34 tackles, 1 sack, 2 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 2vs.PurdueW 35–⁠28110010
Sep 9atNorth CarolinaW 47–⁠35330000
Sep 16vs.ClemsonL 21–⁠47100000
Sep 23vs.Kent StateW 42–⁠3322000
Sep 30vs.Murray StateW 55–⁠10200000
Oct 5atNC StateL 25–⁠39100000
Oct 14vs.Boston CollegeL 42–⁠45652110
Oct 21atFlorida StateW 31–⁠28430000
Oct 28atWake ForestL 32–⁠42420000
Nov 11vs.VirginiaW 38–⁠21110000
Nov 18vs.SyracuseW 56–⁠10410000
Nov 25atKentuckyW 44–⁠17420000
Dec 30 ✦vs.Mississippi StateL 27–⁠31000001

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.