Receiver, North Dakota, 2016–18
Travis Toivonen
- Number
- No. 11
- Height
- 6′3″
- Weight
- 205 lb
- Hometown
- Lubbock, TX
- Born
- Apr 22, 1998
Travis Toivonen played receiver at North Dakota (2016–18).
Career highs
6catches, career highat Bowling Green, 2016Team titles: Big Sky champions, 2016
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2016 | North Dakota | 6 | 58 | 9.7 | 0 | 24 |
| 2017 | North Dakota | 4 | 64 | 16.0 | 0 | 32 |
| 2018 | North Dakota | 5 | 14 | 2.8 | 0 | 4 |
| Career | 15 | 136 | 9.1 | 0 | 32 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2016 | North Dakota | 11 | WR | ||
| 2017 | North Dakota | 11 | WR | ||
| 2018 | North Dakota | 11 | WR | 6′3″ | 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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2016 | North Dakota (FCS) | 12 | -0.04 | – | – | -0.5 | – |
| 2017 | North Dakota (FCS) | 7 | 0.49 | – | – | 3.4 | – |
| 2018 | North Dakota (FCS) | 7 | -0.37 | – | – | -2.6 | – |
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
2018 North Dakota 1 game, 5 catches, 14 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 8 | at | L 3–45 | 5 | 14 | 0 | 4 | – |
No box score in the source for Aug 30 vs. Mississippi Valley State; Sep 15 at Sam Houston; Sep 22 vs. Idaho State; Sep 29 at Northern Colorado; Oct 13 vs. Montana; Oct 21 at Sacramento State; Oct 27 vs. Weber State; Nov 3 at Idaho; Nov 10 vs. Portland State; Nov 17 at Northern Arizona, so those games are not listed.
2017 North Dakota 1 game, 4 catches, 64 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Aug 31 | at | L 16–37 | 4 | 64 | 0 | 32 | – |
No box score in the source for Sep 9 vs. Missouri State; Sep 16 at South Dakota; Sep 23 vs. Montana State; Oct 1 at UC Davis; Oct 7 vs. Northern Colorado; Oct 14 at Montana; Oct 21 vs. Sacramento State; Oct 28 at Portland State; Nov 5 at Southern Utah; Nov 11 vs. Eastern Washington, so those games are not listed.
2016 North Dakota 1 game, 6 catches, 58 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 10 | at | L 26–27 | 6 | 58 | 0 | 24 | 5 |
No box score in the source for Sep 1 at Stony Brook; Sep 17 vs. South Dakota; Sep 24 at Montana State; Oct 1 vs. Cal Poly; Oct 9 at Sacramento State; Oct 15 vs. Southern Utah; Oct 22 at Idaho State; Oct 29 vs. Weber State; Nov 5 at Northern Colorado; Nov 12 vs. Northern Arizona; Dec 3 vs. Richmond, so those games are not listed.
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.
