Running back, North Dakota State (from Holy Cross), 2024–⁠26

Nyeoti Punni

Number
No. 4
Height
6′1″
Weight
225 lb
Class (2026)
Senior
Hometown
Lebanon, NH

Nyeoti Punni plays running back for North Dakota State, after Holy Cross (2024–⁠25). Last time out, against Nevada: 11 carries, 46 yards; 1 catch, 1 yard.

2026 so far

175 rushing yards

Last game: 11 carries, 46 yards; 1 catch, 1 yard vs. Nevada, W 31–⁠17

Next game: at New Mexico, Oct 24

Game by game this season, rushing yards
  1. 60JXST
  2. 29FOR
  3. 19@AF
  4. 4@SAC
  5. 17WYO
  6. 0@UNLV
  7. 46NEV

Filled bars: wins; outlined: losses.

Career highs

131rushing yards, career highat Bucknell, 20252rushing touchdowns, career highat Bucknell, 2025

Team titles: Patriot League champions, 2024

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Holy Cross122.002
2025Holy Cross704155.9353
2026North Dakota State381754.6025
Career1095925.4353

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Holy Cross4RBSo.
2025Holy Cross4RBJr.
2026North Dakota State4RBSr.6′1″225

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/playPctileMedianTotalUsage
2025Holy Cross (FCS)720.0742nd (n=576)0.105.29%
2026North Dakota State38-0.12––-4.78%

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). From CollegeFootballData, 2013 on.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2026North Dakota State28%3.001.100.9019%

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 North Dakota State 7 games, 175 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Aug 29vs.Jacksonville StateW 33–⁠7860025––
Sep 5vs.FordhamW 38–⁠0729012––
Sep 12atAir ForceW 38–⁠3231901528
Sep 19atSacramento StateW 31–⁠103404––
Oct 3vs.WyomingW 28–⁠0517015––
Oct 10atUNLVL 7–⁠131000––
Oct 17vs.NevadaW 31–⁠17114601211
2025 Holy Cross 12 games, 415 rushing yards, 3 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30atNorthern IllinoisL 17–⁠191−500––
Sep 6atNew HampshireL 16–⁠191707––
Sep 13vs.Rhode IslandL 7–⁠92905––
Sep 20atYaleL 10–⁠28636011––
Sep 27atFordhamL 21–⁠26423010––
Oct 4vs.HarvardL 24–⁠59673049––
Oct 18atRichmondW 28–⁠22124711516
Oct 25vs.ColgateL 28–⁠29849020––
Nov 1vs.LafayetteL 13–⁠211303––
Nov 8atLehighL 3–⁠383203––
Nov 15atBucknellW 37–⁠2015131253125
Nov 22vs.GeorgetownW 42–⁠71140016––
2024 Holy Cross 1 game, 2 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Nov 23atGeorgetownW 34–⁠01202––

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.