Linebacker, BYU, 2014–⁠18

Adam Pulsipher

Number
No. 41
Height
6′1″
Weight
220 lb
Class (2018)
Senior
Hometown
Temecula, CA

Adam Pulsipher played linebacker at BYU (2014–⁠18).

Career highs

8tackles, career hightwice; last at Wisconsin, 2018

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksPDHur
2016BYU16101.5000
2017BYU54291000
2018BYU22100010
Career92492.5010

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2014BYU41LBRS
2015BYU41LBFr.
2016BYU41LBSo.
2017BYU41LBJr.
2018BYU41LBSr.6′1″220

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 BYU 7 games, 22 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 1atArizonaW 28–⁠2310000
Sep 15atWisconsinW 24–⁠2183000
Sep 22vs.McNeeseW 30–⁠331001
Sep 29atWashingtonL 7–⁠3520000
Nov 3atBoise StateL 16–⁠2122000
Nov 10atMassachusettsW 35–⁠1610000
Dec 21 ✦vs.Western MichiganW 49–⁠1854000
2017 BYU 13 games, 54 tackles
DateOpponentResultTklSoloTFLSacksPD
Aug 26vs.Portland StateW 20–⁠675000
Sep 2vs.LSUL 0–⁠2743100
Sep 9vs.UtahL 13–⁠1911000
Sep 16vs.WisconsinL 6–⁠4021000
Sep 29atUtah StateL 24–⁠4030000
Oct 6vs.Boise StateL 7–⁠2465000
Oct 14atMississippi StateL 10–⁠3530000
Oct 21atEast CarolinaL 17–⁠3371000
Oct 28vs.San José StateW 41–⁠2054000
Nov 4atFresno StateL 13–⁠2053000
Nov 10atUNLVW 31–⁠2143000
Nov 18vs.MassachusettsL 10–⁠1652000
Nov 25atHawai’iW 30–⁠2021000
2016 BYU 7 games, 16 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 24vs.West VirginiaL 32–⁠3511000
Sep 30vs.ToledoW 55–⁠53860.500
Oct 8atMichigan StateW 31–⁠1410000
Oct 14vs.Mississippi StateW 28–⁠2111100
Nov 5atCincinnatiW 20–⁠320000
Nov 12vs.Southern UtahW 37–⁠710000
Nov 19vs.MassachusettsW 51–⁠922000

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.