Linebacker, Kansas State, 2013–⁠16

Charmeachealle Moore

Lettered 2012–⁠16 (school media guide)

Number
No. 52
Height
6′0″
Hometown
Dallas, TX

Charmeachealle Moore played linebacker at Kansas State (2013–⁠16).

Career highs

8tackles, career hightwice; last at Baylor, 2016

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Kansas State765551.522

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTklTFLSacksPBUFF
2012N1040400–1
2013N135272211
2015E8 of 1332739––––

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
2013Kansas State52LB
2014Kansas State52LB
2015Kansas State52LB
2016Kansas State52LB6′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 Kansas State 13 games, 76 tackles, 1.5 sacks
DateOpponentResultTklSoloTFLSacksPD
Sep 2atStanfordL 13–⁠2643000
Sep 17vs.Florida AtlanticW 63–⁠743110
Sep 24vs.Missouri StateW 35–⁠052100
Oct 1atWest VirginiaL 16–⁠1744100
Oct 8vs.Texas TechW 44–⁠3876000
Oct 15atOklahomaL 17–⁠3875000
Oct 22vs.TexasW 24–⁠2155100
Oct 29atIowa StateW 31–⁠26830.50.50
Nov 5vs.Oklahoma StateL 37–⁠4377000
Nov 19atBaylorW 42–⁠2187001
Nov 26vs.KansasW 34–⁠1965000
Dec 3atTCUW 30–⁠6530.501
Dec 28 ✦vs.Texas A&MW 33–⁠2862000

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.