Pittsburgh
- SP+
- +6.0 (#47)
- FPI
- +1.8 (#57)
- SRS
- +3.9 (#49)
- Resume
- #85
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, 2017
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, 2017
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 Pittsburgh 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 Pittsburgh.
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, 2017
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.
- Ben DinucciQB159 plays · +0.177 pts/play · 117th of 226 QBs0.53WAR0.26 to 0.78
- Darrin HallRB120 plays · +0.153 pts/play · 80th of 352 RBs0.34WAR0.24 to 0.44
- Kenny PickettQB91 plays · +0.180 pts/play · 153rd of 226 QBs0.31WAR0.16 to 0.46
- Jester WeahWR59 plays · +0.172 pts/play · 45th of 426 WRs0.19WAR0.12 to 0.26
- Max BrowneQB78 plays · +0.125 pts/play · 179th of 226 QBs0.18WAR0.06 to 0.32
- Qadree OllisonRB71 plays · +0.130 pts/play · 185th of 352 RBs0.17WAR0.12 to 0.22
- Alex KessmanPK15 plays · +0.465 pts/play · 36th of 110 kickers0.13WAR0.07 to 0.18
- Rafael Araujo-LopesWR42 plays · +0.121 pts/play · 203rd of 426 WRs0.09WAR0.07 to 0.12
Every player (14)
- Quadree HendersonWR42 plays · +0.100 pts/play · 260th of 426 WRs0.08WAR0.04 to 0.12
- Chawntez MossRB27 plays · +0.123 pts/play · 262nd of 352 RBs0.06WAR0.04 to 0.08
- Maurice FfrenchWR6 plays · +0.082 pts/play · 417th of 426 WRs0.01WAR0.00 to 0.02
- Chris ClarkTE14 plays · +0.005 pts/play · 67th of 199 TEs0.00WAR−0.01 to 0.02
- Matt FlanaganTE16 plays · −0.006 pts/play · 195th of 199 TEs0.00WAR−0.02 to 0.02
- Ryan WinslowP48 plays · −0.053 pts/play · 90th of 95 punters−0.05WAR−0.14 to 0.03
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 Pittsburgh'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, 2017
- Roster talent: 660, 34th of 130 in FBSRoster talent247Sports' talent composite: the recruiting ratings of every player on the roster, transfers included.
- Recruiting: 196, 39th of 130 in FBSRecruitingAverage 247Sports class score over this season's class and the three before it.
- Returning production: 38%, 103rd of 128 in FBSReturning productionShare of last season's production (expected points added) by players still on the roster.
- SP+ rating: +6.0, 47th of 128 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
Pittsburgh's SP+ of +6.0 is 1.0 points below the +7.0 its roster talent predicts, 71st of 128 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, 2017
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 Pittsburgh's own. A call that differs gives up the gap to the best option; gaps under one point are close calls, and the 3 clear-cut ones account for 0.04 of the 0.10 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
- at SYRQ4 14:55 4th & 6 at SYR 38, down 7Kicked a field goal; the numbers favored going for it−1.8 pts
- at VTQ4 14:13 4th & 7 at VT 15, down 3Went for it; the numbers favored a field goal−1.5 pts
- at VTQ4 4:14 4th & 9 at PITT 34, down 6Punted; the numbers favored going for it−1.2 pts
- vs UVAQ4 11:09 4th & 2 at UVA 12, up 14Kicked a field goal; the numbers favored going for it (close call)−1.0 pts
- at SYRQ2 7:26 4th & 4 at SYR 31, up 4Kicked a field goal; the numbers favored going for it (close call)−0.7 pts
- vs UNCQ1 2:59 4th & 1 at PITT 40, down 11Punted; the numbers favored going for it (close call)−0.7 pts
- vs NCSUQ3 2:32 4th & 4 at PITT 40, down 7Punted; the numbers favored going for it (close call)−0.6 pts
- vs YSUQ3 13:35 4th & 2 at YSU 44, up 21Punted; the numbers favored going for it (close call)−0.4 pts
Every call this season (97)
- Q2 8:584th & 1 at PITT 48, up 14 · Went for itAgreed
- Q2 5:134th & 1 at YSU 6, up 14 · Went for itAgreed
- Q3 13:354th & 2 at YSU 44, up 21 · PuntedClose call
- Q3 4:444th & 22 at PITT 30, up 14 · PuntedAgreed
- Q4 10:404th & 10 at YSU 10, up 14 · Kicked a field goalAgreed
- Q4 1:514th & 1 at PITT 46, tied · Went for itAgreed
- Q1 11:344th & 9 at PITT 18, down 7 · PuntedAgreed
- Q1 8:034th & 18 at PITT 30, down 7 · PuntedAgreed
- Q2 14:174th & 1 at PSU 36, down 14 · Went for itAgreed
- Q2 12:184th & 22 at PSU 44, down 14 · PuntedAgreed
- Q2 1:124th & 10 at PSU 10, down 14 · Kicked a field goalAgreed
- Q3 10:414th & 2 at PITT 13, down 11 · PuntedClose call
- Q3 6:034th & 6 at PSU 6, down 18 · Kicked a field goalAgreed
- Q3 2:264th & 19 at PITT 25, down 15 · PuntedAgreed
- Q4 2:364th & 4 at PITT 31, down 19 · Went for itAgreed
- Q4 1:014th & 1 at PSU 34, down 19 · Went for itAgreed
- Q4 0:114th & 8 at PSU 8, down 19 · Went for itClose call
- Q1 11:024th & 2 at PITT 33, down 7 · PuntedAgreed
- Q1 5:054th & 16 at PITT 42, down 14 · PuntedAgreed
- Q2 14:554th & 5 at OKST 46, down 21 · Went for itAgreed
- Q2 12:014th & 4 at PITT 26, down 28 · PuntedClose call
- Q2 5:294th & 6 at PITT 29, down 35 · PuntedAgreed
- Q3 11:514th & 24 at OKST 40, down 35 · PuntedAgreed
- Q3 6:364th & 1 at OKST 28, down 42 · Went for itAgreed
- Q3 2:344th & 11 at PITT 41, down 42 · PuntedAgreed
- Q4 4:314th & 7 at OKST 31, down 38 · Kicked a field goalAgreed
- Q1 9:534th & 9 at GT 32, up 7 · Kicked a field goalAgreed
- Q1 6:194th & 12 at PITT 25, tied · PuntedAgreed
- Q2 13:354th & 4 at PITT 48, down 7 · PuntedClose call
- Q2 6:084th & 6 at PITT 47, tied · PuntedAgreed
- Q3 12:594th & 7 at PITT 20, down 4 · PuntedAgreed
- Q3 4:364th & 5 at PITT 40, down 11 · PuntedAgreed
- Q4 15:004th & 25 at PITT 32, down 11 · PuntedAgreed
- Q4 7:184th & 6 at PITT 8, down 11 · PuntedClose call
- Q4 5:294th & 14 at GT 35, down 18 · Went for itClose call
- Q4 2:244th & 3 at PITT 26, down 18 · Went for itAgreed
- Q4 0:034th & 10 at PITT 40, down 18 · Went for itAgreed
- Q1 11:304th & 4 at PITT 31, down 3 · PuntedAgreed
- Q1 7:184th & 2 at PITT 34, down 3 · PuntedClose call
- Q1 5:514th & 1 at PITT 34, down 3 · PuntedClose call
- Q2 13:124th & 7 at PITT 23, up 4 · PuntedAgreed
- Q2 7:264th & 4 at SYR 31, up 4 · Kicked a field goalClose call
- Q2 5:314th & 9 at SYR 46, up 7 · PuntedClose call
- Q3 11:324th & 5 at SYR 24, tied · Kicked a field goalAgreed
- Q3 6:594th & 8 at PITT 27, down 4 · PuntedAgreed
- Q4 14:554th & 6 at SYR 38, down 7 · Kicked a field goal−1.8 pts
- Q1 10:364th & 2 at PITT 42, tied · PuntedClose call
- Q1 0:554th & 3 at PITT 32, down 7 · PuntedAgreed
- Q1 0:554th & 7 at PITT 39, tied · PuntedAgreed
- Q2 13:404th & 8 at NCSU 41, down 7 · PuntedClose call
- Q3 12:364th & 5 at PITT 16, tied · PuntedAgreed
- Q3 8:414th & 16 at PITT 38, tied · PuntedAgreed
- Q3 2:324th & 4 at PITT 40, down 7 · PuntedClose call
- Q4 7:564th & 8 at NCSU 26, down 14 · Kicked a field goalAgreed
- Q4 6:284th & 10 at NCSU 42, down 11 · Went for itAgreed
- Q1 12:204th & 3 at DUKE 45, tied · PuntedClose call
- Q1 5:544th & 21 at DUKE 48, up 7 · PuntedAgreed
- Q2 13:304th & 1 at DUKE 42, up 4 · Went for itAgreed
- Q2 3:454th & 13 at DUKE 29, up 4 · Kicked a field goalAgreed
- Q2 0:154th & 15 at DUKE 37, up 4 · Kicked a field goalAgreed
- Q3 14:564th & 15 at PITT 32, up 4 · PuntedAgreed
- Q3 8:284th & 4 at PITT 43, down 3 · PuntedClose call
- Q3 3:184th & 1 at DUKE 43, down 3 · Went for itAgreed
- Q4 1:414th & 6 at DUKE 27, up 4 · Kicked a field goalAgreed
- Q1 15:004th & 4 at PITT 31, tied · PuntedAgreed
- Q1 6:474th & 11 at PITT 24, up 7 · PuntedAgreed
- Q2 7:154th & 8 at UVA 25, up 14 · Kicked a field goalAgreed
- Q2 4:124th & 10 at PITT 37, up 21 · PuntedAgreed
- Q4 11:094th & 2 at UVA 12, up 14 · Kicked a field goalClose call
- Q4 3:054th & 3 at PITT 8, up 17 · PuntedAgreed
- Q1 10:324th & 8 at PITT 37, down 7 · PuntedAgreed
- Q2 9:434th & 7 at PITT 28, down 3 · PuntedAgreed
- Q2 6:214th & 9 at VT 48, down 3 · PuntedAgreed
- Q2 1:144th & 5 at VT 15, down 3 · Kicked a field goalAgreed
- Q3 13:314th & 5 at PITT 30, down 3 · PuntedAgreed
- Q3 11:414th & 7 at PITT 47, down 3 · PuntedAgreed
- Q4 14:134th & 7 at VT 15, down 3 · Went for it−1.5 pts
- Q4 4:144th & 9 at PITT 34, down 6 · Punted−1.2 pts
- Q4 1:024th & 4 at PITT 25, down 6 · Went for itAgreed
- Q4 0:034th & 1 at VT 1, down 6 · Went for itAgreed
- Q1 11:164th & 5 at PITT 42, tied · PuntedAgreed
- Q1 6:454th & 4 at MIA 28, tied · Kicked a field goalClose call
- Q2 10:544th & 10 at MIA 49, up 3 · PuntedAgreed
- Q3 12:194th & 7 at PITT 40, up 3 · PuntedAgreed
- Q3 7:504th & 2 at PITT 23, up 3 · PuntedAgreed
- Q4 13:544th & 11 at PITT 34, up 10 · PuntedAgreed
- Q4 9:584th & 5 at PITT 41, up 10 · PuntedAgreed
- Q4 2:544th & 6 at MIA 22, up 10 · Went for itClose 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
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, 2017
53rd of 130 FBS teams at beating the model's pregame expectations
Expected wins adds up Pittsburgh's chance of winning each game as the model saw it at kickoff - a 70% favorite counts 0.7.
What moved it, 2017
Every game starts at Pittsburgh'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.07
- Possession & field position−0.09
- Clock+0.07
- Timeouts−0.15
- Less the pregame edge, counted before kickoff+0.57
Game by game
- YSUW 28-21 vs YSU85% → 80%Before kickoff +35 · On the field −5: Scoreboard +19, Timeouts −14
- PSUL 14-33 at PSU6% → 1%Before kickoff −44 · On the field −6: Scoreboard −10
- OKSTL 21-59 vs OKST19% → 0%Before kickoff −31 · On the field −19: Scoreboard −25, Clock −1
- GTL 17-35 at GT28% → 1%Before kickoff −22 · On the field −28: Scoreboard −29, Possession & field position −1
- RICEW 42-10 vs RICE91% → 100%Before kickoff +41 · On the field +9: Scoreboard +11
- SYRL 24-27 at SYR37% → 12%Before kickoff −13 · On the field −25: Scoreboard −22, Possession & field position −2
- NCSUL 17-35 vs NCSU20% → 1%Before kickoff −30 · On the field −19: Scoreboard −28, Clock −1
- DUKEW 24-17 at DUKE23% → 94%Before kickoff −27 · On the field +72: Scoreboard +57, Clock +4
- UVAW 31-14 vs UVA50% → 99%Before kickoff 0 · On the field +49: Scoreboard +44, Timeouts +2
- UNCL 31-34 vs UNC76% → 5%Before kickoff +26 · On the field −71: Scoreboard −53, Clock −3
- VTL 14-20 at VT17% → 15%Before kickoff −33 · On the field −2: Scoreboard −17, Possession & field position +1
- MIAW 24-14 vs MIA19% → 97%Before kickoff −31 · On the field +78: Scoreboard +45, Timeouts +2
Points of win probability, from Pittsburgh's side.
Closest call
PITT 28-27 CIN (2024) - Pittsburgh dropped to a 4.3% win probability before pulling it out.
Season arc, 2017
Every completed game this season, in order - each tile is Pittsburgh's own win-probability curve.
Biggest swings of 2017
The largest single-play change in Pittsburgh's win probability this season - one snap that moved the outcome the most.
Stolen wins
Pittsburgh'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
Pittsburgh'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
Pittsburgh'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
Pittsburgh's most-played opponents across the whole archive - open one for the full head-to-head history.