Safety, Tulsa (from Colorado), 2018–⁠23

L.J. Wallace

Lettered 2018, 2022 at Colorado (school media guide)

Number
No. 22
Height
6′2″
Weight
210 lb
Class (2023)
Senior
Hometown
Atwater, CA

L.J. Wallace played safety at Colorado (2018) and Tulsa (2020–⁠23).

Career highs

10tackles, career highat Navy, 2022

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2018Colorado1000000
2021Tulsa272100100
2022Tulsa39250.50020
Career67460.50120

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
2018Colorado22SYr 1
2020Tulsa22SYr 3
2021Tulsa22SYr 4
2022Tulsa22SYr 5
2023Tulsa22SSr. (Yr 6)6′2″210

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

2022 Tulsa 9 games, 39 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Sep 3atWyomingL 37–⁠40100.5000
Sep 10vs.Northern IllinoisW 38–⁠35420000
Sep 24atOle MissL 27–⁠35330000
Oct 1vs.CincinnatiL 21–⁠31420000
Oct 8atNavyL 21–⁠531040000
Oct 29vs.SMUL 34–⁠45410001
Nov 5vs.TulaneL 13–⁠27220000
Nov 10atMemphisL 10–⁠26550000
Nov 26atHoustonW 37–⁠30660001
2021 Tulsa 10 games, 27 tackles, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 2vs.UC DavisL 17–⁠19410000
Sep 11atOklahoma StateL 23–⁠28210000
Sep 18atOhio StateL 20–⁠41540000
Oct 1vs.HoustonL 10–⁠45110000
Oct 16atSouth FloridaW 32–⁠31110000
Oct 29vs.NavyL 17–⁠20110000
Nov 13atTulaneW 20–⁠13220000
Nov 20vs.TempleW 44–⁠10330000
Nov 27atSMUW 34–⁠31760000
Dec 20 ✦vs.Old DominionW 30–⁠17110010
2018 Colorado 1 game, 1 tackle
DateOpponentResultTklSoloTFLSacksIntPD
Aug 31vs.Colorado StateW 45–⁠13100000

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.