Defensive line, Bethune-Cookman, 2025–⁠26

Lewon Lurry Jr.

Number
No. 10
Height
6′3″
Weight
240 lb
Class (2026)
Sophomore
Hometown
Miami, FL

Lewon Lurry Jr. plays defensive line for Bethune-Cookman. Last time out, at Alabama A&M: 2 tackles. Lurry leads Bethune-Cookman in sacks this season.

2026 so far

16 tackles, 2 sacks, 1 INT

Last game: 2 tackles at Alabama A&M, L 17–⁠55

Next game: vs. Jackson State, Oct 24

Game by game this season, tackles
  1. 3@UCF
  2. 2STET
  3. 5VUL
  4. 2SCST
  5. 2ALST
  6. 2@AAMU

Filled bars: wins; outlined: losses.

Defense

Tackles, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamTklSoloTFLSacksIntPDHur
2025Bethune-Cookman320.50000
2026Bethune-Cookman1654.52102
Career19752102

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
2025Bethune-Cookman10DLFr.
2026Bethune-Cookman10DLSo.6′3″240

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

2026 Bethune-Cookman 6 games, 16 tackles, 2 sacks, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 3atUCFL 6–⁠73321000
Sep 12vs.StetsonW 43–⁠18200.5010
Sep 19vs.Virginia LynchburgW 62–⁠3512100
Sep 26vs.South Carolina StateL 21–⁠31210000
Oct 3vs.Alabama StateW 16–⁠10211100
Oct 10atAlabama A&ML 17–⁠55200000

No box score in the source for Oct 17 at Mississippi Valley State, so that game is not listed.

2025 Bethune-Cookman 2 games, 3 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Aug 29atFlorida InternationalL 9–⁠42110000
Sep 6atMiamiL 3–⁠45210.5000

No box score in the source for Nov 22 at Florida A&M, so that game is not listed.

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.