Defensive back, Fordham, 2017–⁠18

Lawrence Menyah

Number
No. 14
Height
6′2″
Weight
201 lb
Hometown
Leander, TX

Lawrence Menyah played defensive back at Fordham (2017–⁠18).

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksPDHur
2017Fordham520000
2018Fordham440000
Career960000

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGAstTkl
20151 of 111

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: 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.PosHtWt
2017Fordham14DB
2018Fordham14DB6′2″201

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 Fordham 1 game, 4 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 1atCharlotteL 10–⁠3444000

No box score in the source for Sep 8 at Richmond; Sep 15 vs. Stony Brook; Sep 22 vs. Central Connecticut; Oct 6 vs. Georgetown; Oct 13 at Lehigh; Oct 20 vs. Bryant; Oct 27 vs. Lafayette; Nov 3 vs. Colgate; Nov 10 at Holy Cross; Nov 17 at Bucknell, so those games are not listed.

2017 Fordham 1 game, 5 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 1atArmyL 6–⁠6452000

No box score in the source for Sep 9 at Central Connecticut; Sep 16 vs. Eastern Washington; Sep 23 at Bryant; Sep 30 vs. Yale; Oct 7 at Lafayette; Oct 14 at Colgate; Oct 21 at Georgetown; Oct 28 vs. Lehigh; Nov 4 vs. Holy Cross; Nov 18 vs. Bucknell, so those games are 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.