3.87–3.63
Strength and score are read from SJS's side, the same minutes at both ends: PP = SJS power play · PK = TOR power play · Leading = SJS ahead · ST = each club's own power play.
SJS attacks◀ all strengths
How to read this map
One rink, both teams: SJS attacks the left net, TOR the right. Every attempt is a Gaussian bump of height = its model xG. The controls switch the surface (xG heatmap ↔ vs league) and the markers; vs league compares this game against a typical NHL team-game under the same filter (2026-27 regular season, 283 games), so a 5v5 view is measured against league 5v5.
A strength or score filter is read from SJS's side and mirrored for TOR: “SJS PP” shows SJS's power-play attempts on the left and TOR's shorthanded attempts on the right — the same minutes of the game at both ends. Empty-net attempts are excluded unless you include them. The Player control narrows the map and the rows beneath it to the attempts by either club while one player was on the ice (for a goalie, while he was in net); his own attempts wear a blue ring. vs league switches off while a player is picked — the league baseline is a whole team-game, which one player's slice is not. Hover any attempt for the shooter, the result, its xG, and the inputs behind it: clock, strength, score, shot type, distance, angle, handedness, rush/rebound, what happened just before, and the goalie or the blocker.
What each side produced
all strengths · this gameThe Maple Leafs beat the Sharks 3–1 at home in a game the chances called about even, SJS 3.9 to TOR 3.6 in expected goals. The Maple Leafs power play made 1.1 xG on 11 attempts.
Counts come from the shot table behind the map: empty-net attempts and the shootout are excluded, so the goals here can trail the official final by an empty-netter or the shootout's deciding goal. Same numbers as the post-game cards.
As the game went
all situations · this gameHow to read this
One line: cumulative SJS minus TOR expected goals. Above zero SJS is ahead on chances, below zero TOR is. Shaded bands are power plays in the side's colour; vertical lines are goals.
Goals
this game| Team | Scorer | Period | Time | xG | |
|---|---|---|---|---|---|
| SJS | Mason Marchment | 1st | 13:54 | 0.19 | |
| TOR | Auston Matthews | 2nd | 19:48 | PP | 0.10 |
| TOR | Gavin McKenna | 3rd | 4:56 | PP | 0.13 |
| TOR | Nick Paul | 3rd | 19:20 | EN | 0.45 |
Skaters
all · whole game · this gameHow to read this
Every skater: on-ice xG against to the left of zero, for to the right, his own attempts as the solid bar, a hash at the net. The slim track under the name is ice time. The chart opens sorted by net, best first; pick another key to re-order it, and click the same key again to flip it. A name opens the player's page. Pick a period and every bar re-lays for that period alone on the same scale as the whole game, so the three periods add up to it; a skater who did not play in it fades to the bottom.
SJS
TOR
Lines & pairs
all · whole game · this gameHow to read this
The units that actually played together most at the chosen strength — forward lines and defence pairs at 5v5, the whole group on the ice on the power play or the kill — each with when it was on the ice at that strength across the game clock (period and power-play bands behind the strip) and on-ice xG against / for while the whole unit was out, at that strength only. Sorted by time together; pick another key to re-order, and a name opens the player's page. Pick a period and the strip veils the rest of the game while the bars re-lay for that period alone, on the whole game's scale.
SJS
TOR
Matchups
5v5 · this gameHow to read this
Rows are SJS's skaters, columns TOR's, grouped the way they played: forward lines (L1 = the line that played together most), then defence pairs. Each cell covers the five-on-five time those two players shared the ice. Its colour is the club that out-chanced the other in that time — expected goals for minus against — and the stronger the colour, the bigger the margin. Each cell is also raised: the taller the block, the longer the two shared the ice, up to full height at 12:00 of five-on-five time. A grey cell means they met and it came out even; an open, flat one means they never met at five-on-five.
The first row and column are the goalies. A goalie is in net for every five-on-five second, so a skater's cell against the other side's goalie is all of that skater's five-on-five time against that team — the rest of his row or column added up — and the corner where the two goalies meet is the game's five-on-five. Those cells cover far more time than any pair, so they reach full colour sooner and stand at full height, a wall along each edge of the grid. A goalie change adds a second goalie row or column, each covering his own time.
Linemates share the ice, so a line against a line reads as a block. The margin is a total, not a rate: a long matchup has room to build a big gap and a thirty-second one does not — which is what the height is there to show: a tall, strong cell is the game's story; a short, strong one is a moment. Hover (or tap) any cell for the exact time together, the xG each way, attempts and goals. One game — a strong cell is what happened, not what would happen again.
The prediction, scored
🔒 pregame · this gameBefore puck drop the engine made TOR a 55.8% favorite, expecting a 2.94–3.32 game — TOR won 1–3, so the call landed. Every number in this section was issued before the game and is never re-graded.
| pred. xG | actual xG | pred. 5v5 | actual 5v5 | pred. ST | actual PP | |
|---|---|---|---|---|---|---|
| SJS | 2.94 | 3.87 | 1.89 | 3.03 | 0.79 | 0.64 |
| TOR | 3.32 | 3.63 | 2.06 | 1.80 | 1.02 | 1.06 |
Predicted 5v5 / special-teams portions come from the predicted map's strength splits (one shared scale per team pins the all-strengths total to its expected goals), so they don't sum exactly — the remainder is 4v4, 3v3, and other mixed states. The actual columns are the card's own counts (empty-net attempts excluded); the actual PP column is power-play xG only, the same bucket the predicted map's special-teams view draws.
The pregame score grid
🔒 pregame · this gameThe likeliest finals the engine saw before the game, with what actually happened marked — ■ SJS · ■ TOR.
| Likeliest finals (SJS–TOR) | probability | |
|---|---|---|
| 3–3 | 7.0% | tied after regulation — OT/SO decides |
| 2–2 | 6.5% | tied after regulation — OT/SO decides |
| 2–4 | 4.4% | |
| 4–4 | 4.3% | tied after regulation — OT/SO decides |
| 1–3 | 3.6% | what happened |
Scoreline odds are the engine's own grid: each team's goals as a Poisson count, with the fitted adjustment for how often games end tied after regulation (ρ = 0.35), so these odds and the headline win probability come from the same numbers. The OT/SO layer is a separate fitted model and is already inside the headline win probability.
The pregame read
🔒 pregame · this gameThe engine made TOR a 55.8% favorite — TOR controls 53.0% of the predicted xG. Of SJS's 2.94 expected goals, 1.89 should come at 5v5 and 0.79 on the power play; TOR projects 2.06 at 5v5 and 1.02 on the power play. The logistic challenger put the home side at 54.3%, Elo at 60.5%.
Where the engine expected the goals
🔒 pregame · this gameThe predicted surface, issued before puck drop — not this game's shots (those are the card's map above). SJS attacks the left net, TOR the right; each end multiplies where the attacking team generates xG this season by where its opponent concedes it, scaled so each end totals the engine's expected goals. Actual shots lays the game's unblocked attempts on top: × goals, • on net, ◦ missed.
Tale of the tape
season to dateHow each team fares on its own, season to date: per-game xG rates with league rank (of 32). Rank 1 is best on every row — orange ranks sit in the top third of the league, gray in the bottom third.
| SJS | TOR | |
|---|---|---|
| 2.70 (26th) | Offense xG for / game |
2.73 (24th) |
| 3.74 (32nd) | Defense xG against / game |
3.17 (24th) |
| 0.74 (19th) | Power play PP xG / game |
0.75 (17th) |
| 1.12 (32nd) | Penalty kill PP xG conceded / game |
0.82 (21st) |
Season-to-date form as of the site's latest build, shown for context — the ratings the engine actually used were its own as-of-game-day state. Replay this matchup in the lab →