Running back, Oregon State, 2024–⁠26

Cornell Hatcher Jr.

Number
No. 3
Height
6′0″
Weight
210 lb
Class (2026)
Sophomore
Hometown
Corona, CA

Cornell Hatcher Jr. plays running back for Oregon State. Last time out, against Washington State: 10 carries, 65 yards, 1 TD; 1 catch, 7 yards. Hatcher leads Oregon State in rushing touchdowns this season.

2026 so far

214 rushing yards, 4 TD

Last game: 10 carries, 65 yards, 1 TD; 1 catch, 7 yards vs. Washington State, W 48–⁠30

Next game: at Fresno State, Oct 31

Game by game this season, rushing yards
  1. 7@HOU
  2. 17TTU
  3. 26MONT
  4. 19@UTEP
  5. 51@CSU
  6. 29SDSU
  7. 65WSU

Filled bars: wins; outlined: losses.

Career highs

93rushing yards, career highvs. Houston, 2025

Team titles: Pac-12 champions, 2024

Rushing

Rushing yards, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2025Oregon State522925.6242
2026Oregon State422145.1427
Career945065.4642

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Oregon State3RBRS
2025Oregon State3RBFr.
2026Oregon State3RBSo.6′0″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.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsageAdj. rush
2025Oregon State610.0536th (n=576)0.103.39%0.09
2026Oregon State440.1254th (n=478)0.105.29%–

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.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2025Oregon State63%3.801.501.9014%
2026Oregon State52%3.401.100.9016%

Where his yards came from, per carry: line yards are the ones credited to the blockers (the first few, and losses), second level the yards 5 to 10 past the line, open field those beyond 10. Success: carries that kept the offense on schedule. Stuffed: carries stopped at or behind the line. From CollegeFootballData, FBS games, 2025 on.

Game by game

2026 Oregon State 7 games, 214 rushing yards, 4 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5atHoustonL 20–⁠333703––
Sep 12vs.Texas TechL 24–⁠35417010––
Sep 19vs.MontanaW 52–⁠17426114––
Sep 26atUTEPW 33–⁠7619014––
Oct 3atColorado StateW 56–⁠26751115––
Oct 10vs.San Diego StateW 66–⁠1482911115
Oct 17vs.Washington StateW 48–⁠30106512717
2025 Oregon State 9 games, 292 rushing yards, 2 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30vs.CaliforniaL 15–⁠3411001014
Sep 20atOregonL 7–⁠4141407––
Sep 26vs.HoustonL 24–⁠27179311826
Oct 4atApp StateL 23–⁠27417010115
Oct 11vs.Wake ForestL 14–⁠39743129––
Oct 18vs.LafayetteW 45–⁠13563042––
Nov 1vs.Washington StateW 10–⁠7624091−8
Nov 15atTulsaL 14–⁠31620010––
Nov 29atWashington StateL 8–⁠322805––

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.