Defensive end, Akron, 2016
Daumantas Venckus
- Number
- No. 19
- Height
- 6′5″
- Hometown
- Weston, FL
Daumantas Venckus played defensive end at Akron (2016).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Akron | 41 | 16 | 4 | 1 | 2 | 1 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2015 | 12 of 13 | 4 | 5 | 9 |
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 |
|---|---|---|---|---|
| 2016 | Akron | 19 | DE | 6′5″ |
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 Akron 11 games, 41 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 10 | at Wisconsin | L 10–54 | 2 | 0 | 0.5 | 0 | 0 |
| Sep 17 | at Marshall | W 65–38 | 6 | 0 | 1 | 0 | 0 |
| Sep 24 | vs. App State | L 38–45 | 2 | 2 | 0 | 0 | 0 |
| Oct 1 | at Kent State | W 31–27 | 1 | 0 | 0.5 | 0 | 0 |
| Oct 8 | vs. Miami (OH) | W 35–13 | 4 | 3 | 1 | 1 | 0 |
| Oct 15 | vs. Western Michigan | L 0–41 | 6 | 1 | 0 | 0 | 0 |
| Oct 22 | at Ball State | W 35–25 | 7 | 3 | 1 | 0 | 1 |
| Oct 27 | at Buffalo | L 20–41 | 5 | 1 | 0 | 0 | 1 |
| Nov 2 | vs. Toledo | L 17–48 | 3 | 2 | 0 | 0 | 0 |
| Nov 9 | vs. Bowling Green | L 28–38 | 1 | 0 | 0 | 0 | 0 |
| Nov 22 | at Ohio | L 3–9 | 4 | 4 | 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.