Receiver, North Dakota, 2022–26
Sam Strandell
- Number
- No. 88
- Height
- 6′3″
- Weight
- 221 lb
- Class (2026)
- Senior
- Hometown
- Grand Forks, ND
Sam Strandell plays receiver for North Dakota. Last time out, at Northern Iowa: 2 catches, 13 yards.
2026 so far
8 catches, 84 yards, 1 TD
Last game: 2 catches, 13 yards at Northern Iowa, L 17–24
Next game: at South Dakota, Oct 24
Filled bars: wins; outlined: losses.
Receiving
* The season in progress, so far.
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2023 | North Dakota | 1 | 10 | 10.0 | 0 | 10 |
| 2024 | North Dakota | 5 | 25 | 5.0 | 0 | 9 |
| 2025 | North Dakota | 1 | 8 | 8.0 | 0 | 8 |
| 2026 | North Dakota | 8 | 84 | 10.5 | 1 | 40 |
| Career | 15 | 127 | 8.5 | 1 | 40 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | North Dakota | 88 | WR | RS | ||
| 2023 | North Dakota | 88 | WR | Fr. | ||
| 2024 | North Dakota | 88 | WR | So. | ||
| 2025 | North Dakota | 88 | WR | Jr. | ||
| 2026 | North Dakota | 88 | WR | Sr. | 6′3″ | 221 |
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 |
|---|---|---|---|---|---|---|---|
| 2023 | North Dakota (FCS) | 1 | 0.39 | – | – | 0.4 | – |
| 2024 | North Dakota (FCS) | 5 | 0.40 | – | – | 2.0 | – |
| 2025 | North Dakota (FCS) | 3 | -0.25 | – | – | -0.8 | – |
| 2026 | North Dakota (FCS) | 14 | 0.20 | – | – | 2.9 | – |
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 North Dakota 5 games, 8 catches, 84 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 27 | vs. Long Island University | W 42–21 | 2 | 45 | 0 | 40 |
| Sep 5 | vs. St. Thomas (MN) | W 62–26 | 2 | 9 | 1 | 6 |
| Sep 12 | at Portland State | W 47–23 | 2 | 17 | 0 | 12 |
| Sep 19 | at Nebraska | L 7–34 | – | – | – | – |
| Oct 10 | at Northern Iowa | L 17–24 | 2 | 13 | 0 | 7 |
2025 North Dakota 1 game, 1 catch, 8 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Nov 8 | vs. North Dakota State | L 10–15 | 1 | 8 | 0 | 8 |
2024 North Dakota 4 games, 5 catches, 25 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 7 | vs. Montana | W 27–24 | 1 | 4 | 0 | 4 |
| Sep 14 | vs. Idaho State | W 52–28 | 1 | 7 | 0 | 7 |
| Sep 28 | vs. Murray State | W 72–35 | 2 | 13 | 0 | 9 |
| Nov 2 | at Indiana State | L 31–35 | 1 | 1 | 0 | 1 |
2023 North Dakota 1 game, 1 catch, 10 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Oct 7 | vs. Western Illinois | W 49–10 | 1 | 10 | 0 | 10 |
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.