Linebacker, Washington State, 2013–16
Paris Taylor
- Number
- No. 20
- Height
- 6′3″
- Hometown
- Orlando, FL
Paris Taylor played linebacker at Washington State (2013–16).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Washington State | 20 | 13 | 0 | 0 | 0 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2014 | 6 of 12 | 1 | 1 | 2 |
| 2015 | 8 of 13 | 0 | 1 | 1 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2013 | Washington State | 20 | LB | |
| 2014 | Washington State | 20 | LB | |
| 2015 | Washington State | 20 | LB | |
| 2016 | Washington State | 20 | LB | 6′3″ |
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.
Game by game
2016 Washington State 8 games, 20 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 10 | at Boise State | L 28–31 | 2 | 2 | 0 | 0 | 0 |
| Sep 17 | vs. Idaho | W 56–6 | 3 | 1 | 0 | 0 | 0 |
| Oct 1 | vs. Oregon | W 51–33 | 1 | 1 | 0 | 0 | 0 |
| Oct 8 | at Stanford | W 42–16 | 6 | 2 | 0 | 0 | 0 |
| Oct 15 | vs. UCLA | W 27–21 | 1 | 1 | 0 | 0 | 0 |
| Nov 5 | vs. Arizona | W 69–7 | 3 | 2 | 0 | 0 | 0 |
| Nov 12 | vs. California | W 56–21 | 1 | 1 | 0 | 0 | 0 |
| Nov 19 | at Colorado | L 24–38 | 3 | 3 | 0 | 0 | 0 |
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.