Defensive end, Wyoming, 2016–17
Taniela Lolohea
- Number
- No. 58
- Height
- 6′1″
- Weight
- 253 lb
- Hometown
- Hawthorne, CA
Taniela Lolohea played defensive end at Wyoming (2016–17).
Career highs
2sacks, career highvs. Central Michigan, 2017Defense
Season lines from CollegeFootballData, regular season and bowls.
On the roster
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
2017 Wyoming 8 games, 18 tackles, 3 sacks
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 9 | vs. Gardner-Webb | W 27–0 | 3 | 2 | 0 | 0 | 0 |
| Sep 16 | vs. Oregon | L 13–49 | 1 | 0 | 0.5 | 0 | 0 |
| Sep 30 | vs. Texas State | W 45–10 | 3 | 2 | 1 | 0 | 0 |
| Oct 14 | at Utah State | W 28–23 | 2 | 1 | 0 | 0 | 0 |
| Oct 28 | vs. New Mexico | W 42–3 | 5 | 1 | 1 | 1 | 0 |
| Nov 18 | vs. Fresno State | L 7–13 | 0 | 0 | 0 | 0 | 1 |
| Nov 25 | at San José State | L 17–20 | 1 | 1 | 0 | 0 | 0 |
| Dec 22 ✦ | vs. Central Michigan | W 37–14 | 3 | 2 | 2 | 2 | 0 |
2016 Wyoming 11 games, 16 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 10 | at Nebraska | L 17–52 | 1 | 1 | 1 | 0 | 0 |
| Sep 17 | vs. UC Davis | W 45–22 | 1 | 1 | 1 | 1 | 0 |
| Oct 1 | at Colorado State | W 38–17 | 2 | 1 | 0 | 0 | 0 |
| Oct 8 | vs. Air Force | W 35–26 | 3 | 1 | 0 | 0 | 0 |
| Oct 22 | at Nevada | W 42–34 | 2 | 1 | 0 | 0 | 0 |
| Oct 29 | vs. Boise State | W 30–28 | 1 | 0 | 0 | 0 | 0 |
| Nov 5 | vs.Utah State | W 52–28 | 1 | 0 | 0 | 0 | 2 |
| Nov 12 | at UNLV | L 66–69 | 1 | 1 | 0 | 0 | 0 |
| Nov 26 | atNew Mexico | L 35–56 | 2 | 2 | 0 | 0 | 0 |
| Dec 3 | vs. San Diego State | L 24–27 | 1 | 1 | 0 | 0 | 0 |
| Dec 21 ✦ | vs. BYU | L 21–24 | 1 | 1 | 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.