Virginia Tech
- SP+
- +8.0 (#38)
- FPI
- +4.5 (#48)
- SRS
- +4.5 (#46)
- Resume
- #41
Next game
Advanced stats
CollegeFootballData's play-by-play measures of how efficient and explosive a team was, placed against every other FBS team. How it works →
Profile vs. FBS, 2019
Farther out is better on every spoke. Dashed ring: the FBS median.
- EPA per playExpected points added on an average snap: how much each play moved the scoring odds.
- Success rateShare of snaps that stayed on schedule: half the yards needed on 1st down, 70% on 2nd, all of them on 3rd or 4th.
- ExplosivenessAverage EPA on the successful snaps: how big the good plays were.
- Rushing EPAEPA per designed run.
- Passing EPAEPA per pass play.
- Standard downsSuccess rate on downs where either a run or a pass makes sense, like 1st and 10 or 3rd and 2.
- Passing downsSuccess rate on downs that all but force a pass, like 2nd and 8 or longer, or 3rd and 5 or longer.
- Line yardsRushing yards per carry credited to the offensive line, weighting the first few yards most.
- Stuff rateShare of runs stopped at or behind the line of scrimmage.
- HavocShare of snaps with a tackle for loss, sack, forced fumble, interception or pass breakup.
Percentiles among the 130 FBS teams this season, where higher is better for the offense and the defense alike (a defense's numbers are what it allowed). The line in each bar is the FBS median. Garbage time excluded. Source: CollegeFootballData.
Expected points
YardLine's expected-points model values every snap by what a drive from that spot is worth on average, so a drive can be judged against where it started. How it works →
Drives vs. expectation, 2019
Points over expected per drive, from where each drive started.
Per drive against an average FBS opponent, neutral field.
Points over expected per trip inside the opponent's 40.
Average expected points where drives started.
Every snap has an expected-points value: what a drive from that spot, down and distance is worth on average. A drive over expected beat its starting spot; defense counts what Virginia Tech allowed, so lower is better. The adjusted number fits every team against the opponents it actually played, so it leans toward average early in a season. Ranks are among FBS teams.
Game by game
Bars above the line: better than expected for Virginia Tech.
Players
YardLine's player model credits every play's value to the players involved, so each one's season can be measured in wins above a typical backup. How it works →
Players, 2019
Quarterback is the most valuable starting slot by a wide margin: the gap between a top-decile and a median FBS quarterback is about twice the gap at any other position.
- Hendon HookerQB216 plays · +0.224 pts/play · 88th of 228 QBs0.90WAR0.46 to 1.33
- Ryan WillisQB95 plays · +0.258 pts/play · 132nd of 228 QBs0.46WAR0.29 to 0.62
- Deshawn McCleaseRB144 plays · +0.157 pts/play · 89th of 349 RBs0.42WAR0.31 to 0.53
- Quincy PattersonQB64 plays · +0.277 pts/play · 157th of 228 QBs0.33WAR0.21 to 0.47
- Tre TurnerWR67 plays · +0.151 pts/play · 79th of 439 WRs0.19WAR0.12 to 0.26
- Keshawn KingRB59 plays · +0.153 pts/play · 222nd of 349 RBs0.17WAR0.14 to 0.20
- Brian JohnsonPK14 plays · +0.436 pts/play · 63rd of 114 kickers0.11WAR0.07 to 0.15
- Damon HazeltonWR46 plays · +0.112 pts/play · 219th of 439 WRs0.10WAR0.03 to 0.16
Every player (12)
- Dalton KeeneTE27 plays · +0.115 pts/play · 31st of 207 TEs0.06WAR0.03 to 0.09
- James MitchellTE21 plays · +0.099 pts/play · 56th of 207 TEs0.04WAR0.01 to 0.07
- Hezekiah GrimsleyWR8 plays · +0.142 pts/play · 421st of 439 WRs0.02WAR0.01 to 0.03
- Oscar BradburnP42 plays · +0.025 pts/play · 85th of 100 punters0.02WAR−0.02 to 0.07
By position group, against FBS
Linemen and defenders are valued as units, in points per game against the median FBS unit, because play-by-play doesn't say who was on the field. Players are valued against a replacement-level backup, so the two aren't added together.
Wins above replacement credits each play's expected points to the players involved, adjusted for the opponent, and compares Virginia Tech's players with a typical backup; 53 points make a win. Only snaps while the game was in doubt count, so a starter on a team that blows opponents out plays fewer of them: read value per play beside WAR. The line under each player (or the range on a phone) is the 90% interval. Ranks are among FBS teams and players. How this works
Talent and roster
How much talent the roster had, by recruiting ratings, and how much of it showed up on the field, against every other FBS team. How it works →
What it had and what it did, 2019
- Roster talent: 696, 29th of 130 in FBSRoster talent247Sports' talent composite: the recruiting ratings of every player on the roster, transfers included.
- Recruiting: 214, 30th of 130 in FBSRecruitingAverage 247Sports class score over this season's class and the three before it.
- Returning production: 75%, 31st of 130 in FBSReturning productionShare of last season's production (expected points added) by players still on the roster.
- SP+ rating: +8.0, 38th of 130 in FBSSP+ ratingThe result: Bill Connelly's opponent-adjusted rating, points per game better than an average FBS team.
Ranks and bars among the 130 FBS teams with a talent rating this season, best first; the line in each bar is the FBS median.
Talent conversion
Virginia Tech's SP+ of +8.0 is 1.2 points above the +6.8 its roster talent predicts, 59th of 130 in FBS.
The same comparison on each side of the ball, positive is better for both.
Conversion by season
Fourth downs
YardLine's fourth-down model values going for it, kicking and punting on every real fourth down, so each call can be checked against the numbers. How it works →
Fourth-down calls vs. the numbers, 2019
Calls that matched the option with the best modeled win probability.
Summed over every call that differed, in points of win probability.
Went for it when going beat every other option by a point or more.
Each real fourth down is valued three ways (go for it, kick, punt) from the score, clock and field position before the snap, using league-wide odds rather than Virginia Tech's own. A call that differs gives up the gap to the best option; gaps under one point are close calls, and the 6 clear-cut ones account for 0.13 of the 0.19 expected wins. The model sees the situation, not the injury report, so a call it disagrees with can still be right. Ranks are among FBS teams; 1st gave up the least.
Costliest calls against the numbers
- vs UNCQ4 6:25 4th & 2 at VT 49, tiedPunted; the numbers favored going for it−5.1 pts
- vs WAKEQ3 2:38 4th & 1 at VT 35, up 6Punted; the numbers favored going for it−3.1 pts
- at UKQ4 12:47 4th & 3 at UK 9, up 3Kicked a field goal; the numbers favored going for it−1.5 pts
- at MIAQ3 13:11 4th & 1 at VT 34, up 21Punted; the numbers favored going for it−1.4 pts
- at BCQ3 12:56 4th & 3 at BC 47, down 14Punted; the numbers favored going for it−1.1 pts
- vs DUKEQ2 10:15 4th & 1 at VT 34, down 4Punted; the numbers favored going for it−1.0 pts
- vs URIQ2 0:01 4th & 24 at URI 44, up 11Went for it; the numbers favored punting (close call)−0.9 pts
- vs DUKEQ3 9:04 4th & 2 at VT 18, down 18Punted; the numbers favored going for it (close call)−0.7 pts
Every call this season (93)
- Q1 14:094th & 10 at VT 35, tied · PuntedAgreed
- Q1 11:544th & 1 at VT 28, down 7 · PuntedClose call
- Q1 3:004th & 10 at VT 16, tied · PuntedAgreed
- Q2 6:094th & 7 at VT 33, down 7 · PuntedAgreed
- Q3 12:564th & 3 at BC 47, down 14 · Punted−1.1 pts
- Q3 11:414th & 1 at BC 33, down 14 · Went for itAgreed
- Q4 12:154th & 9 at VT 3, down 7 · PuntedAgreed
- Q4 7:534th & 7 at BC 41, down 14 · Went for itAgreed
- Q4 7:534th & 1 at BC 13, down 14 · Went for itAgreed
- Q1 15:004th & 7 at VT 39, tied · PuntedAgreed
- Q1 5:374th & 5 at FUR 16, tied · Kicked a field goalAgreed
- Q2 14:564th & 23 at VT 12, down 4 · PuntedAgreed
- Q2 1:394th & 15 at FUR 32, down 11 · Kicked a field goalAgreed
- Q3 5:214th & 10 at VT 34, up 3 · PuntedAgreed
- Q4 7:484th & 6 at VT 33, up 3 · PuntedAgreed
- Q1 10:064th & 7 at midfield, tied · PuntedAgreed
- Q1 7:184th & 6 at DUKE 46, tied · PuntedClose call
- Q1 0:274th & 2 at DUKE 2, tied · Kicked a field goalClose call
- Q2 10:154th & 1 at VT 34, down 4 · Punted−1.0 pts
- Q2 4:254th & 7 at DUKE 40, down 11 · PuntedClose call
- Q3 9:044th & 2 at VT 18, down 18 · PuntedClose call
- Q3 3:384th & 1 at VT 43, down 21 · Went for itAgreed
- Q1 6:234th & 5 at VT 25, up 7 · PuntedAgreed
- Q2 0:534th & 14 at VT 27, up 28 · PuntedAgreed
- Q3 13:114th & 1 at VT 34, up 21 · Punted−1.4 pts
- Q3 7:434th & 11 at VT 24, up 14 · PuntedAgreed
- Q3 0:244th & 8 at VT 23, up 14 · PuntedAgreed
- Q4 6:074th & 14 at VT 15, up 14 · PuntedAgreed
- Q4 4:064th & 9 at VT 26, up 6 · PuntedAgreed
- Q1 10:474th & 4 at VT 42, down 10 · PuntedAgreed
- Q2 11:104th & 7 at VT 32, down 3 · PuntedAgreed
- Q3 15:004th & 4 at VT 31, up 4 · PuntedAgreed
- Q3 9:274th & 21 at UNC 39, down 3 · PuntedAgreed
- Q4 9:294th & 5 at UNC 5, down 3 · Kicked a field goalAgreed
- Q4 6:254th & 2 at VT 49, tied · Punted−5.1 pts
- Q4 0:454th & 2 at VT 39, tied · PuntedAgreed
- Q1 12:324th & 6 at VT 29, tied · PuntedAgreed
- Q1 9:364th & 15 at VT 4, tied · PuntedAgreed
- Q1 7:264th & 3 at VT 42, down 7 · PuntedClose call
- Q1 4:594th & 5 at VT 48, down 7 · PuntedAgreed
- Q1 1:504th & 4 at ND 20, down 7 · Went for itAgreed
- Q2 10:544th & 6 at VT 29, down 7 · PuntedAgreed
- Q2 8:504th & 3 at VT 17, down 7 · PuntedClose call
- Q3 11:004th & 6 at ND 26, tied · Kicked a field goalAgreed
- Q3 5:004th & 5 at VT 31, up 3 · PuntedAgreed
- Q4 13:254th & 5 at ND 7, up 3 · Kicked a field goalAgreed
- Q4 3:224th & 13 at VT 41, up 6 · PuntedAgreed
- Q1 11:094th & 2 at WAKE 41, tied · Went for itAgreed
- Q1 5:334th & 18 at WAKE 18, tied · Kicked a field goalAgreed
- Q1 1:194th & 4 at VT 34, tied · PuntedAgreed
- Q2 14:494th & 2 at WAKE 28, tied · Went for itAgreed
- Q2 7:474th & 4 at WAKE 14, tied · Kicked a field goalClose call
- Q2 5:404th & 10 at VT 40, down 4 · PuntedAgreed
- Q3 5:304th & 7 at WAKE 18, up 3 · Kicked a field goalAgreed
- Q3 2:384th & 1 at VT 35, up 6 · Punted−3.1 pts
- Q4 4:574th & 4 at midfield, up 12 · PuntedClose call
- Q1 13:184th & 3 at VT 37, tied · PuntedClose call
- Q2 12:094th & 1 at GT 5, up 14 · Went for itAgreed
- Q2 8:134th & 9 at GT 38, up 21 · PuntedClose call
- Q2 1:164th & 4 at GT 4, up 28 · Kicked a field goalClose call
- Q3 14:584th & 15 at VT 46, up 31 · PuntedAgreed
- Q3 8:074th & 6 at midfield, up 38 · PuntedClose call
- Q4 8:204th & 5 at GT 5, up 45 · Went for itClose call
- Q1 15:004th & 6 at VT 40, tied · PuntedAgreed
- Q1 11:274th & 12 at VT 38, tied · PuntedAgreed
- Q1 9:064th & 1 at PITT 38, tied · Went for itAgreed
- Q2 11:174th & 30 at VT 33, up 14 · PuntedAgreed
- Q3 11:404th & 24 at VT 6, up 21 · PuntedAgreed
- Q3 8:074th & 4 at VT 14, up 21 · PuntedAgreed
- Q3 1:194th & 22 at PITT 42, up 21 · PuntedAgreed
- Q4 6:194th & 8 at VT 44, up 28 · PuntedAgreed
- Q1 10:194th & 3 at VT 32, down 6 · PuntedAgreed
- Q1 3:264th & 3 at UVA 3, down 6 · Kicked a field goalClose call
- Q2 10:484th & 6 at VT 24, down 10 · PuntedAgreed
- Q2 7:044th & 11 at VT 46, down 10 · PuntedAgreed
- Q2 2:064th & 8 at UVA 8, down 10 · Kicked a field goalAgreed
- Q3 11:134th & 7 at VT 34, tied · PuntedAgreed
- Q4 10:584th & 12 at UVA 29, tied · Kicked a field goalAgreed
- Q1 11:154th & 13 at UK 36, tied · Kicked a field goalAgreed
- Q2 5:024th & 7 at VT 31, up 10 · PuntedAgreed
- Q3 4:124th & 8 at UK 34, tied · Went for itAgreed
- Q3 3:134th & 10 at UK 22, tied · Kicked a field goalAgreed
- Q4 12:474th & 3 at UK 9, up 3 · Kicked a field goal−1.5 pts
- Q4 8:254th & 4 at VT 45, up 6 · PuntedClose call
After touchdowns: kick or go for two?
Tries that matched the option with the better modeled win probability.
Summed over every try that differed, in points of win probability.
Went for two when it beat kicking by a point or more.
Costliest tries against the numbers
- at MIAQ4 1:03 Touchdown, up 6 before the tryKicked; the numbers favored going for two (close call)−0.8 pts
- vs WAKEQ4 4:38 Touchdown, up 18 before the tryKicked; the numbers favored going for two (close call)−0.4 pts
- vs WAKEQ4 11:44 Touchdown, up 12 before the tryWent for two; the numbers favored kicking (close call)−0.3 pts
Win probability
YardLine's model estimates each team's chance of winning before kickoff and again after every play, from the score, clock, down, distance and field position. How it works →
Record vs. expectation, 2019
58th of 130 FBS teams at beating the model's pregame expectations
Expected wins adds up Virginia Tech's chance of winning each game as the model saw it at kickoff - a 70% favorite counts 0.7.
What moved it, 2019
Every game starts at Virginia Tech's pregame chance; everything after that is the field. The model's own breakdown of each game's final play splits the on-field part by what drove it, and the parts add up exactly. How it works →
- Scoreboard+0.37
- Possession & field position−0.04
- Clock+0.19
- Timeouts−0.20
- Less the pregame edge, counted before kickoff−0.13
Game by game
- BCL 28-35 at BC63% → 5%Before kickoff +13 · On the field −58: Scoreboard −41, Timeouts −2
- ODUW 31-17 vs ODU97% → 99%Before kickoff +47 · On the field +2: Scoreboard +7
- FURW 24-17 vs FUR95% → 97%Before kickoff +45 · On the field +2: Scoreboard +10, Timeouts +1
- DUKEL 10-45 vs DUKE63% → 0%Before kickoff +13 · On the field −63: Scoreboard −62, Clock −1
- MIAW 42-35 at MIA19% → 78%Before kickoff −31 · On the field +59: Scoreboard +41, Possession & field position −5
- URIW 34-17 vs URI97% → 99%Before kickoff +47 · On the field +2: Scoreboard +7
- UNCW 43-41 vs UNC40% → 86%Before kickoff −10 · On the field +47: Scoreboard +25, Timeouts −18
- NDL 20-21 at ND12% → 6%Before kickoff −38 · On the field −6: Scoreboard −18, Possession & field position −1
- WAKEW 36-17 vs WAKE44% → 99%Before kickoff −6 · On the field +55: Scoreboard +48, Possession & field position −1
- GTW 45-0 at GT70% → 100%Before kickoff +20 · On the field +30: Scoreboard +35, Clock +1
- PITTW 28-0 vs PITT63% → 100%Before kickoff +13 · On the field +37: Scoreboard +37
- UVAL 30-39 at UVA54% → 4%Before kickoff +4 · On the field −50: Scoreboard −40, Possession & field position +2
- UKL 30-37 at UK58% → 22%Before kickoff +8 · On the field −36: Scoreboard −13, Possession & field position −3
Points of win probability, from Virginia Tech's side.
Closest call
CAL 34-42 VT (2025) - Virginia Tech dropped to a 5.3% win probability before pulling it out.
Season arc, 2019
Every completed game this season, in order - each tile is Virginia Tech's own win-probability curve.
Biggest swings of 2019
The largest single-play change in Virginia Tech's win probability this season - one snap that moved the outcome the most.
Stolen wins
Virginia Tech's own lowest win probability at any point in a game it went on to win, across the whole archive - the deepest holes it climbed out of.
Let it slip
Virginia Tech's own highest win probability at any point in a game it went on to lose, across the whole archive - the biggest leads it didn't hold.
Stock & rivalries
Stock
Virginia Tech's leaguewide Elo rating, tracked like a stock price - built from game results and margins, not the model's own win-probability predictions.
Series & rivalries
Virginia Tech's most-played opponents across the whole archive - open one for the full head-to-head history.