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, 2020
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 127 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, 2020
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, 2020
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.
- Kenny PickettQB341 plays · +0.092 pts/play · 63rd of 212 QBs0.58WAR0.03 to 1.16
- Vincent Davis Jr.RB145 plays · +0.146 pts/play · 58th of 338 RBs0.40WAR0.26 to 0.52
- Jordan AddisonWR73 plays · +0.151 pts/play · 19th of 409 WRs0.21WAR0.13 to 0.28
- DJ TurnerWR64 plays · +0.133 pts/play · 48th of 409 WRs0.16WAR0.09 to 0.23
- A.J. DavisRB54 plays · +0.154 pts/play · 211th of 338 RBs0.16WAR0.12 to 0.19
- Joey YellenQB66 plays · +0.105 pts/play · 151st of 212 QBs0.13WAR0.02 to 0.24
- Shocky Jacques-LouisWR41 plays · +0.142 pts/play · 102nd of 409 WRs0.11WAR0.07 to 0.16
- Alex KessmanPK26 plays · +0.195 pts/play · 2nd of 97 kickers0.09WAR0.03 to 0.15
Every player (14)
- Jared WayneWR26 plays · +0.169 pts/play · 172nd of 409 WRs0.08WAR0.05 to 0.11
- Taysir MackWR37 plays · +0.107 pts/play · 194th of 409 WRs0.07WAR0.02 to 0.12
- Kirk ChristodoulouP37 plays · +0.073 pts/play · 19th of 77 punters0.05WAR0.00 to 0.10
- Tre TiptonWR16 plays · +0.122 pts/play · 314th of 409 WRs0.04WAR0.02 to 0.05
- Todd SibleyRB8 plays · +0.192 pts/play · 284th of 338 RBs0.03WAR0.02 to 0.03
- Lucas KrullTE3 plays · +0.030 pts/play · 137th of 191 TEs0.00WAR0.00 to 0.01
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, 2020
- Roster talent: 653, 36th of 127 in FBSRoster talent247Sports' talent composite: the recruiting ratings of every player on the roster, transfers included.
- Recruiting: 192, 47th of 127 in FBSRecruitingAverage 247Sports class score over this season's class and the three before it.
- Returning production: 74%, 44th of 127 in FBSReturning productionShare of last season's production (expected points added) by players still on the roster.
- SP+ rating: +6.0, 41st of 127 in FBSSP+ ratingThe result: Bill Connelly's opponent-adjusted rating, points per game better than an average FBS team.
Ranks and bars among the 127 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 above the +5.0 its roster talent predicts, 53rd of 127 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, 2020
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 2 clear-cut ones account for 0.05 of the 0.12 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 FSUQ4 12:01 4th & 1 at FSU 1, up 14Kicked a field goal; the numbers favored going for it−3.1 pts
- vs VTQ2 10:24 4th & 1 at PITT 15, up 9Punted; the numbers favored going for it−2.0 pts
- at GTQ4 8:04 4th & 4 at GT 4, up 10Kicked a field goal; the numbers favored going for it (close call)−0.9 pts
- at BCQ2 0:00 4th & 7 at BC 37, down 3Kicked a field goal; the numbers favored going for it (close call)−0.9 pts
- at MIAQ3 0:31 4th & 3 at MIA 12, down 12Kicked a field goal; the numbers favored going for it (close call)−0.7 pts
- vs SYRQ2 0:03 4th & 12 at SYR 28, up 4Went for it; the numbers favored a field goal (close call)−0.7 pts
- at MIAQ2 12:48 4th & 10 at PITT 42, down 7Went for it; the numbers favored punting (close call)−0.6 pts
- vs NDQ2 12:06 4th & 7 at ND 37, down 4Punted; the numbers favored going for it (close call)−0.5 pts
Every call this season (96)
- Q1 12:404th & 11 at PITT 9, tied · PuntedAgreed
- Q2 12:444th & 3 at SYR 19, up 4 · Kicked a field goalClose call
- Q2 3:164th & 4 at SYR 37, up 4 · Went for itAgreed
- Q2 0:034th & 12 at SYR 28, up 4 · Went for itClose call
- Q3 15:004th & 7 at PITT 28, up 4 · PuntedAgreed
- Q4 14:534th & 10 at PITT 40, up 11 · PuntedAgreed
- Q4 10:444th & 3 at SYR 26, up 11 · Kicked a field goalClose call
- Q4 6:364th & 6 at PITT 10, up 11 · PuntedAgreed
- Q1 13:024th & 10 at LOU 27, tied · Kicked a field goalAgreed
- Q1 9:104th & 8 at LOU 23, up 3 · Kicked a field goalAgreed
- Q2 15:004th & 8 at LOU 48, up 6 · PuntedAgreed
- Q2 3:114th & 5 at LOU 40, down 4 · Went for itAgreed
- Q2 2:074th & 11 at PITT 35, up 3 · PuntedAgreed
- Q3 11:264th & 16 at LOU 24, up 3 · Kicked a field goalAgreed
- Q3 8:154th & 5 at PITT 30, up 6 · PuntedAgreed
- Q4 10:254th & 4 at LOU 32, up 3 · Went for itAgreed
- Q4 2:434th & 14 at PITT 38, up 3 · PuntedAgreed
- Q1 5:474th & 3 at PITT 42, tied · PuntedClose call
- Q1 1:204th & 9 at PITT 26, down 3 · PuntedAgreed
- Q2 12:564th & 1 at PITT 34, down 10 · PuntedClose call
- Q2 4:504th & 9 at NCSU 9, down 10 · Kicked a field goalAgreed
- Q2 3:524th & 4 at NCSU 35, down 7 · Went for itAgreed
- Q2 0:044th & 7 at NCSU 11, down 7 · Kicked a field goalAgreed
- Q3 12:514th & 1 at NCSU 1, down 4 · Went for itAgreed
- Q3 5:534th & 13 at PITT 17, down 4 · PuntedAgreed
- Q4 10:524th & 8 at NCSU 24, up 3 · Kicked a field goalAgreed
- Q4 5:514th & 1 at NCSU 32, down 1 · Went for itAgreed
- Q1 15:004th & 1 at BC 35, tied · PuntedClose call
- Q1 9:304th & 3 at BC 41, down 3 · Went for itAgreed
- Q2 15:004th & 13 at PITT 6, up 4 · PuntedAgreed
- Q2 4:414th & 7 at PITT 43, down 3 · PuntedAgreed
- Q2 0:004th & 7 at BC 37, down 3 · Kicked a field goalClose call
- Q3 11:124th & 9 at BC 31, down 10 · Kicked a field goalAgreed
- Q3 9:064th & 15 at PITT 20, down 10 · PuntedAgreed
- Q4 12:434th & 7 at PITT 38, down 3 · PuntedAgreed
- Q4 6:294th & 5 at BC 40, down 3 · Went for itAgreed
- Q4 0:404th & 20 at BC 41, down 3 · Kicked a field goalAgreed
- Q1 15:004th & 22 at MIA 43, tied · PuntedAgreed
- Q1 8:154th & 21 at PITT 10, tied · PuntedAgreed
- Q1 5:484th & 13 at PITT 33, down 7 · PuntedAgreed
- Q1 1:504th & 12 at PITT 48, down 7 · PuntedAgreed
- Q2 12:484th & 10 at PITT 42, down 7 · Went for itClose call
- Q2 2:434th & 14 at MIA 15, down 14 · Kicked a field goalAgreed
- Q2 0:084th & 4 at MIA 6, down 11 · Kicked a field goalAgreed
- Q3 11:204th & 15 at MIA 17, down 15 · Kicked a field goalAgreed
- Q3 0:314th & 3 at MIA 12, down 12 · Kicked a field goalClose call
- Q4 14:054th & 10 at PITT 34, down 9 · PuntedAgreed
- Q4 12:124th & 10 at PITT 35, down 9 · PuntedAgreed
- Q4 4:134th & 10 at PITT 46, down 12 · Went for itAgreed
- Q1 7:384th & 10 at ND 27, down 7 · Kicked a field goalAgreed
- Q1 2:104th & 16 at PITT 21, down 4 · PuntedAgreed
- Q2 12:064th & 7 at ND 37, down 4 · PuntedClose call
- Q2 8:544th & 2 at PITT 39, down 11 · PuntedClose call
- Q2 0:114th & 15 at PITT 31, down 18 · PuntedAgreed
- Q3 13:444th & 9 at PITT 37, down 25 · PuntedAgreed
- Q3 0:384th & 7 at ND 47, down 42 · PuntedAgreed
- Q4 11:584th & 2 at PITT 46, down 42 · PuntedClose call
- Q4 7:524th & 20 at PITT 11, down 42 · PuntedAgreed
- Q1 12:314th & 11 at FSU 32, tied · Kicked a field goalAgreed
- Q1 6:184th & 3 at PITT 43, down 4 · PuntedClose call
- Q1 3:564th & 7 at PITT 28, down 11 · PuntedAgreed
- Q2 8:464th & 10 at FSU 27, down 4 · Kicked a field goalAgreed
- Q2 1:264th & 11 at PITT 17, up 10 · PuntedAgreed
- Q3 6:144th & 14 at PITT 15, up 14 · PuntedAgreed
- Q4 12:014th & 1 at FSU 1, up 14 · Kicked a field goal−3.1 pts
- Q4 6:404th & 8 at PITT 27, up 17 · PuntedAgreed
- Q1 11:444th & 4 at VT 4, tied · Kicked a field goalClose call
- Q1 10:004th & 10 at PITT 21, up 3 · PuntedAgreed
- Q1 3:384th & 3 at VT 12, up 3 · Kicked a field goalClose call
- Q2 13:394th & 5 at VT 34, up 6 · Kicked a field goalClose call
- Q2 10:244th & 1 at PITT 15, up 9 · Punted−2.0 pts
- Q2 0:534th & 10 at PITT 30, up 9 · PuntedAgreed
- Q3 12:254th & 10 at VT 35, up 9 · Kicked a field goalAgreed
- Q4 10:594th & 3 at VT 19, up 26 · Went for itAgreed
- Q1 13:504th & 18 at PITT 17, tied · PuntedAgreed
- Q1 10:564th & 7 at PITT 28, down 7 · PuntedAgreed
- Q1 3:034th & 5 at PITT 30, down 24 · PuntedAgreed
- Q2 13:324th & 15 at PITT 40, down 31 · PuntedAgreed
- Q2 9:114th & 3 at CLEM 5, down 31 · Kicked a field goalClose call
- Q2 6:584th & 3 at PITT 32, down 35 · PuntedAgreed
- Q3 8:284th & 7 at PITT 27, down 21 · PuntedAgreed
- Q3 4:364th & 7 at midfield, down 21 · PuntedAgreed
- Q4 9:234th & 6 at PITT 45, down 35 · PuntedAgreed
- Q4 7:074th & 11 at PITT 30, down 35 · PuntedAgreed
- Q4 3:124th & 7 at PITT 11, down 35 · PuntedAgreed
- Q1 13:184th & 1 at GT 1, up 3 · Went for itAgreed
- Q1 2:594th & 5 at PITT 46, down 4 · PuntedAgreed
- Q2 14:464th & 1 at GT 16, down 4 · Went for itAgreed
- Q2 11:424th & 6 at GT 7, down 4 · Kicked a field goalAgreed
- Q2 1:394th & 6 at GT 12, up 6 · Kicked a field goalAgreed
- Q3 7:104th & 17 at PITT 13, up 16 · PuntedAgreed
- Q4 8:044th & 4 at GT 4, up 10 · Kicked a field goalClose 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, 2020
65th of 127 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, 2020
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.96
- Possession & field position+0.01
- Clock−0.19
- Timeouts+0.21
- Less the pregame edge, counted before kickoff−0.59
Game by game
- APSUW 55-0 vs APSU97% → 100%Before kickoff +47 · On the field +3: Scoreboard +4
- SYRW 21-10 vs SYR93% → 96%Before kickoff +43 · On the field +3: Scoreboard +13
- LOUW 23-20 vs LOU55% → 92%Before kickoff +5 · On the field +36: Scoreboard +32, Clock −1
- NCSUL 29-30 vs NCSU84% → 31%Before kickoff +34 · On the field −52: Scoreboard −24, Clock −4
- BCL 30-31 at BC71% → 34%Before kickoff +21 · On the field −37: Timeouts +20, Clock −18
- MIAL 19-31 at MIA22% → 2%Before kickoff −28 · On the field −20: Scoreboard −25, Timeouts −1
- NDL 3-45 vs ND25% → 0%Before kickoff −25 · On the field −25: Scoreboard −31, Clock −1
- FSUW 41-17 at FSU55% → 100%Before kickoff +5 · On the field +45: Scoreboard +48, Clock +2
- VTW 47-14 vs VT38% → 100%Before kickoff −12 · On the field +62: Scoreboard +55, Timeouts −1
- CLEML 17-52 at CLEM5% → 0%Before kickoff −45 · On the field −5: Scoreboard −8
- GTW 34-20 at GT66% → 99%Before kickoff +16 · On the field +33: Scoreboard +42, Clock +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, 2020
Every completed game this season, in order - each tile is Pittsburgh's own win-probability curve.
Biggest swings of 2020
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.