Safety, West Virginia, 2012–⁠16

Jarrod Harper

Number
No. 22
Height
6′0″
Hometown
Frostburg, MD

Jarrod Harper played safety at West Virginia (2012–⁠16).

Career highs

8tackles, career hightwice; last vs. Kansas State, 2016

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016West Virginia71553010

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTklFF
2013N1264101
2015E8 of 1317421–

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
2012West Virginia22S
2013West Virginia22S
2014West Virginia22S
2015West Virginia22S
2016West Virginia22S6′0″

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 West Virginia 13 games, 71 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 3vs.MissouriW 26–⁠1144001
Sep 10vs.Youngstown StateW 38–⁠2165000
Sep 24vs.BYUW 35–⁠3283000
Oct 1vs.Kansas StateW 17–⁠1686000
Oct 15atTexas TechW 48–⁠1744000
Oct 22vs.TCUW 34–⁠1010000
Oct 29atOklahoma StateL 20–⁠3755100
Nov 5vs.KansasW 48–⁠2177000
Nov 12atTexasW 24–⁠2066000
Nov 19vs.OklahomaL 28–⁠5631000
Nov 26atIowa StateW 49–⁠1974100
Dec 3vs.BaylorW 24–⁠2175000
Dec 28 ✦vs.MiamiL 14–⁠3155100
2014 West Virginia 1 game, 1 return, 18 yards
DateOpponentResultTklSoloTFLSacksPD
Sep 13atMarylandW 40–⁠37–––––

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.