Wake Forest, 2012–⁠16

Ryan Janvion

Number
No. 22
Height
5′11″
Hometown
Miami, FL

Ryan Janvion played at Wake Forest (2012–⁠16).

Career highs

8tackles, career highvs. Army, 2016

Defense

SeasonTeamTklSoloTFLSacksIntPDHur
2013Wake Forest––––1––
2016Wake Forest46321.50110
Career46321.50210

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.

Defense before 2016

SeasonGSoloAstTklTFLInt
2013N126134952.51
2014E8 of 12383977––
2015E8 of 12252247––

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
2012Wake Forest22
2013Wake Forest22
2014Wake Forest22
2015Wake Forest22
2016Wake Forest225′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 Wake Forest 10 games, 46 tackles, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 1vs.TulaneW 7–⁠3650000
Sep 10atDukeW 24–⁠14330000
Sep 17vs.DelawareW 38–⁠21310000
Sep 24atIndianaW 33–⁠28650010
Oct 1atNC StateL 16–⁠33420000
Oct 8vs.SyracuseW 28–⁠9531000
Oct 15atFlorida StateL 6–⁠17540000
Oct 29vs.ArmyL 13–⁠21860000
Nov 5vs.VirginiaW 27–⁠20210000
Dec 27 ✦vs.TempleW 34–⁠26420.5001
2013 Wake Forest 1 game, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Nov 9vs.Florida StateL 3–⁠59––––1–

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.