Tight end, Montana State, 2025–26
Rocky Lencioni
- Number
- No. 89
- Height
- 6′3″
- Weight
- 247 lb
- Class (2026)
- Junior
- Hometown
- Bozeman, MT
Rocky Lencioni plays tight end for Montana State. Last time out, at Eastern Washington: 2 catches, 27 yards.
2026 so far
13 catches, 162 yards, 1 TD
Last game: 2 catches, 27 yards at Eastern Washington, W 56–20
Next game: vs. Weber State, Oct 24
Filled bars: wins; outlined: losses.
Career highs
2receiving touchdowns, career highvs. Idaho State, 2025Team titles: Big Sky champions, 2025
Receiving
* The season in progress, so far.
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2025 | Montana State | 19 | 206 | 10.8 | 6 | 34 |
| 2026 | Montana State | 13 | 162 | 12.5 | 1 | 33 |
| Career | 32 | 368 | 11.5 | 7 | 34 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2025 | Montana State | 89 | TE | So. | ||
| 2026 | Montana State | 89 | TE | Jr. | 6′3″ | 247 |
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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2025 | Montana State (FCS) | 24 | 0.79 | – | – | 19.0 | 3% |
| 2026 | Montana State (FCS) | 22 | 0.35 | 40th (n=829) | 0.43 | 7.7 | 5% |
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.
Game by game
2026 Montana State 7 games, 13 catches, 162 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 29 | at Utah Tech | W 54–0 | 1 | 11 | 0 | 11 |
| Sep 5 | vs. Butler | W 51–24 | 3 | 54 | 0 | 33 |
| Sep 12 | at Nevada | W 20–7 | 3 | 35 | 0 | 13 |
| Sep 19 | vs. Central Connecticut | W 35–30 | 2 | 10 | 1 | 9 |
| Sep 26 | vs. Northern Arizona | W 28–14 | 1 | 18 | 0 | 18 |
| Oct 2 | at Idaho | L 34–35 | 1 | 7 | 0 | 7 |
| Oct 17 | at Eastern Washington | W 56–20 | 2 | 27 | 0 | 23 |
2025 Montana State 13 games, 19 catches, 206 yards, 6 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 30 | at Oregon | L 13–59 | 4 | 39 | 0 | 24 |
| Sep 13 | vs. San Diego | W 41–7 | 1 | 6 | 0 | 6 |
| Oct 4 | atNorthern Arizona | W 34–10 | 1 | 3 | 1 | 3 |
| Oct 11 | vs. Idaho State | W 48–14 | 2 | 35 | 2 | 22 |
| Oct 25 | at Cal Poly | W 34–17 | 2 | 26 | 0 | 16 |
| Nov 1 | at Northern Colorado | W 55–7 | 1 | 3 | 1 | 3 |
| Nov 8 | vs. Weber State | W 66–14 | 1 | 4 | 1 | 4 |
| Nov 15 | vs. UC Davis | W 38–17 | – | – | – | – |
| Nov 22 | at Montana | W 31–28 | 1 | 2 | 0 | 2 |
| Dec 6 | vs. Yale | W 21–13 | 1 | 7 | 0 | 7 |
| Dec 12 | vs. Stephen F. Austin | W 44–28 | 2 | 29 | 0 | 21 |
| Dec 20 ✦ | vs.Montana | W 48–23 | 2 | 36 | 1 | 34 |
| Jan 5 ✦ | vs. Illinois State | W 35–34 | 1 | 16 | 0 | 16 |
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.