Quarterback, Idaho State (from Idaho), 2016–19
Gunnar Amos
- Number
- No. 12
- Height
- 6′1″
- Weight
- 191 lb
- Hometown
- Dallas, TX
Gunnar Amos played quarterback at Idaho (2016) and Idaho State (2017–19).
Passing
| Season | Team | Cmp | Att | Pct | Yds | Y/A | TD | Int |
|---|---|---|---|---|---|---|---|---|
| 2016 | Idaho | 3 | 10 | 30.0 | 33 | 3.3 | 0 | 1 |
| 2017 | Idaho State | 0 | 1 | 0.0 | 0 | 0.0 | 0 | 0 |
| 2019 | Idaho State | 7 | 17 | 41.2 | 52 | 3.1 | 0 | 1 |
| Career | 10 | 28 | 35.7 | 85 | 3.0 | 0 | 2 | |
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2016 | Idaho | 6 | 22 | 3.7 | 1 | 10 |
| 2019 | Idaho State | 2 | −3 | −1.5 | 0 | 0 |
| Career | 8 | 19 | 2.4 | 1 | 10 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2016 | Idaho | 12 | QB | ||
| 2017 | Idaho State | 12 | QB | ||
| 2018 | Idaho State | 12 | QB | ||
| 2019 | Idaho State | 12 | QB | 6′1″ | 191 |
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 | Idaho | 13 | -0.47 | – | – | -6.1 | – |
| 2017 | Idaho State (FCS) | 1 | -0.98 | – | – | -1.0 | – |
| 2019 | Idaho State (FCS) | 19 | -0.27 | – | – | -5.1 | – |
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
2019 Idaho State 1 game, 52 passing yards
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Sep 14 | at Utah | L 0–31 | 7 | 17 | 52 | 0 | 1 | −3 |
No box score in the source for Sep 6 vs. Western Colorado; Sep 21 at Northern Iowa; Sep 28 vs. Portland State; Oct 5 at Montana; Oct 12 vs. North Dakota; Oct 19 at Idaho; Oct 26 at Southern Utah; Nov 2 vs. Northern Colorado; Nov 9 vs. Eastern Washington; Nov 23 at Weber State, so those games are not listed.
2017 Idaho State 1 game, 0 passing yards
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Sep 7 | at Utah State | L 13–51 | 0 | 1 | 0 | 0 | 0 | – |
No box score in the source for Sep 1 vs. Western Oregon; Sep 23 at Northern Colorado; Sep 30 vs. Cal Poly; Oct 7 vs. Montana; Oct 15 at Sacramento State; Oct 21 vs. Portland State; Oct 28 at Montana State; Nov 4 vs. UC Davis; Nov 18 at Weber State, so those games are not listed.
2016 Idaho 4 games, 33 passing yards
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Sep 10 | at Washington | L 14–59 | 1 | 4 | 22 | 0 | 1 | 24 |
| Sep 17 | at Washington State | L 6–56 | 1 | 4 | 7 | 0 | 0 | – |
| Oct 15 | vs. New Mexico State | W 55–23 | 1 | 2 | 4 | 0 | 0 | −4 |
| Nov 12 | at Texas State | W 47–14 | – | – | – | – | – | 2 |
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.