Defensive back, UNLV, 2017–⁠20

Drew Tejchman

Number
No. 3
Height
5′11″
Weight
195 lb
Class (2020)
Junior
Hometown
Acworth, GA

Drew Tejchman played defensive back at UNLV (2017–⁠20).

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2017UNLV2100000
2018UNLV4200110
2019UNLV151300000
Career211600110

Receiving

SeasonTeamRecYdsAvgTDLong
2017UNLV713819.7050
2018UNLV111029.3224
Career1824013.3250

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
2017UNLV3DBYr 1
2018UNLV3DBYr 2
2019UNLV3DBYr 3
2020UNLV3DBJr. (Yr 4)5′11″195

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

2019 UNLV 3 games, 15 tackles
DateOpponentResultTklSacksIntPDRecRec ydsRec TD
Aug 31vs.Southern UtahW 56–⁠235000–––
Sep 7vs.Arkansas StateL 17–⁠437000–––
Sep 14atNorthwesternL 14–⁠303000–––
2018 UNLV 8 games, 4 tackles, 1 INT
DateOpponentResultTklSacksIntPDRecRec ydsRec TD
Sep 15vs.Prairie View A&MW 46–⁠17––––1241
Sep 22atArkansas StateL 20–⁠27––––150
Oct 13atUtah StateL 28–⁠59––––3251
Oct 19vs.Air ForceL 35–⁠41––––3190
Oct 27atSan José StateL 37–⁠5010001110
Nov 10atSan Diego StateW 27–⁠2410001100
Nov 17atHawai’iL 28–⁠351011–––
Nov 24vs.NevadaW 34–⁠291000180
2017 UNLV 8 games, 7 catches, 138 yards
DateOpponentResultTklSacksIntPDRecRec ydsRec TD
Sep 2vs.HowardL 40–⁠43––––1340
Oct 7vs.San Diego StateL 10–⁠4110002430
Oct 21vs.Utah StateL 28–⁠52––––170
Oct 28atFresno StateW 26–⁠16––––1−10
Nov 4vs.Hawai’iW 31–⁠231000–––
Nov 10vs.BYUL 21–⁠31––––1500
Nov 17atNew MexicoW 38–⁠35––––150
Nov 25atNevadaL 16–⁠23–––––––

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.