Running back, Kansas, 2019–⁠24

Torry Locklin

Number
No. 12
Height
6′2″
Weight
205 lb
Class (2024)
Senior
Hometown
Rockdale, TX

Torry Locklin played running back at Kansas (2019–⁠24).

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2019Kansas341.302
2021Kansas361173.3236
2022Kansas12322.7112
2023Kansas9404.4019
2024Kansas252.505
Career621983.2336

Defense

SeasonTeamTklSoloTFLSacksPDHur
2021Kansas100000
2022Kansas320000
2023Kansas430000
2024Kansas220000
Career1070000

Receiving

SeasonTeamRecYdsAvgTDLong
2021Kansas3248.0120
2022Kansas815519.4260
2023Kansas44010.0125
2024Kansas23618.0031
Career1725515.0460

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2019Kansas12RBYr 1
2020Kansas12RBYr 2
2021Kansas12RBYr 3
2022Kansas12RBYr 4
2023Kansas12RBYr 5
2024Kansas12RBSr. (Yr 6)6′2″205

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.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsageAdj. rush
2019Kansas3-0.40––-1.2––
2021Kansas40-0.06––-2.37%0.20
2022Kansas250.48––12.05%–
2023Kansas110.31––3.4––
2024Kansas40.10––0.4––

Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Game by game

2024 Kansas 5 games, 5 rushing yards
DateOpponentResultCarRush ydsRush TDTklSacksPD
Sep 21atWest VirginiaL 28–⁠32–––100
Sep 28vs.TCUL 27–⁠38150–––
Oct 5atArizona StateL 31–⁠35––––––
Oct 19vs.HoustonW 42–⁠14–––100
Nov 9vs.Iowa StateW 45–⁠36100–––
2023 Kansas 8 games, 40 rushing yards
DateOpponentResultCarRush ydsRush TDTklSacksPD
Sep 1vs.Missouri StateW 48–⁠17––––––
Sep 8vs.IllinoisW 34–⁠23110100
Sep 23vs.BYUW 38–⁠27–––100
Oct 14atOklahoma StateL 32–⁠39–––100
Nov 11vs.Texas TechL 13–⁠16––––––
Nov 18vs.Kansas StateL 27–⁠314190–––
Nov 25atCincinnatiW 49–⁠164200–––
Dec 26 ✦vs.UNLVW 49–⁠36–––100
2022 Kansas 9 games, 32 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDTklSacksPD
Sep 2vs.Tennessee TechW 56–⁠10130–––
Sep 10atWest VirginiaW 55–⁠42–––100
Sep 17atHoustonW 48–⁠30––––––
Sep 24vs.DukeW 35–⁠27220–––
Oct 15atOklahomaL 42–⁠52––––––
Oct 22atBaylorL 23–⁠35–––100
Nov 19vs.TexasL 14–⁠553100100
Nov 26atKansas StateL 27–⁠476171–––
Dec 28 ✦vs.ArkansasL 53–⁠55––––––
2021 Kansas 9 games, 117 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDTklSacksPD
Sep 3vs.South DakotaW 17–⁠14580–––
Sep 10atCoastal CarolinaL 22–⁠493110–––
Sep 18vs.BaylorL 7–⁠45200–––
Sep 25atDukeL 33–⁠527471–––
Oct 2atIowa StateL 7–⁠5912391–––
Oct 16vs.Texas TechL 14–⁠41380–––
Oct 23vs.OklahomaL 23–⁠35330100
Oct 30atOklahoma StateL 3–⁠55110–––
Nov 6vs.Kansas StateL 10–⁠35––––––
2019 Kansas 2 games, 4 rushing yards
DateOpponentResultCarRush ydsRush TDTklSacksPD
Oct 19atTexasL 48–⁠50220–––
Nov 23atIowa StateL 31–⁠41120–––

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.