Russian Premier League table 2026/2027
- Leader Zenit St. Petersburg 31 pts
- Most above xPts Dynamo Moscow +7.05 against expected points
- Most below xPts Fakel Voronezh −8.54 against expected points
The Russian Premier League table for 2026/2027, with expected goals (xG), xGA and expected points (xPts) beside every club's points. Zenit St. Petersburg top both the table and expected points, on 28.25 xPts.
| # restore the table order | Team | P sort descending | W sort descending | D sort descending | L sort descending | GF sort descending | GA sort descending | GD sort descending | Pts sort descending | xG sort descending | xGA sort descending | xGD sort descending | xPts sort descending | Pts vs xPts sort descending |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Zenit St. Petersburg ZEN | 14 | 10 | 1 | 3 | 32 | 15 | +17 | 31 | 33.13 | 16.89 | +16.24 | 28.25 | +2.75 |
| 2 | Dynamo Moscow DYN | 14 | 10 | 1 | 3 | 23 | 13 | +10 | 31 | 26.73 | 18.69 | +8.04 | 23.95 | +7.05 |
| 3 | FC Spartak Moscow FCS | 14 | 9 | 2 | 3 | 27 | 11 | +16 | 29 | 25.62* | 17.19 | +8.43 | 23.03 | +2.97 |
| 4 | FK Krasnodar FKK | 14 | 7 | 5 | 2 | 25 | 18 | +7 | 26 | 27.61 | 18.44 | +9.17 | 24.93 | +1.07 |
| 5 | CSKA Moscow CSK | 14 | 7 | 5 | 2 | 23 | 16 | +7 | 26 | 30.81 | 25.62 | +5.19 | 22.79 | +3.21 |
| 6 | FC Rostov FCR | 14 | 5 | 4 | 5 | 18 | 19 | −1 | 19 | 19.43 | 18.61 | +0.82 | 19.42 | −0.42 |
| 7 | Krylya Sovetov Samara KRY | 14 | 4 | 6 | 4 | 19 | 20 | −1 | 18 | 23.78 | 25.08 | −1.30 | 19.14 | −1.14 |
| 8 | Rubin Kazan RUB | 14 | 4 | 6 | 4 | 14 | 18 | −4 | 18 | 19.10* | 18.37 | +0.73 | 18.15 | −0.15 |
| 9 | Baltika Kaliningrad BAL | 14 | 4 | 5 | 5 | 17 | 15 | +2 | 17 | 24.36 | 15.70 | +8.66 | 24.61 | −7.61 |
| 10 | Orenburg ORE | 14 | 3 | 8 | 3 | 14 | 14 | 0 | 17 | 24.82 | 23.02 | +1.80 | 20.58 | −3.58 |
| 11 | Dinamo Makhachkala DIN | 14 | 5 | 1 | 8 | 17 | 26 | −9 | 16 | 21.50 | 24.53 | −3.03 | 18.79 | −2.79 |
| 12 | Akhmat Grozny AKH | 14 | 3 | 5 | 6 | 16 | 19 | −3 | 14 | 19.42 | 21.91 | −2.49 | 17.68 | −3.68 |
| 13 | Akron Togliatti AKR | 14 | 2 | 6 | 6 | 17 | 25 | −8 | 12 | 14.61 | 27.64 | −13.03 | 11.00 | +1.00 |
| 14 | Rodina Moscow ROD | 14 | 3 | 3 | 8 | 15 | 29 | −14 | 12 | 15.38 | 33.22 | −17.84 | 9.60 | +2.40 |
| 15 | Lokomotiv Moscow LOK | 14 | 2 | 5 | 7 | 16 | 21 | −5 | 11 | 19.06 | 32.42 | −13.36 | 12.50 | −1.50 |
| 16 | Fakel Voronezh FAK | 14 | 1 | 3 | 10 | 9 | 23 | −14 | 6 | 14.23 | 22.26 | −8.03 | 14.54 | −8.54 |
- More points than xPts
- Fewer points than xPts
- xG is available for 13 of 14 matches for FC Spartak Moscow.
- xG is available for 13 of 14 matches for Rubin Kazan.
- For those clubs the expected columns count only the matches with xG, and Pts vs xPts sets their expected points against the points from those same matches.
How to read this table
- xG
- Expected goals: the summed chance quality of the shots a club took. A chance scored nine times in ten is worth 0.9.
- xGA
- Expected goals against: the same measure for the shots a club allowed.
- xGD
- xG minus xGA: how far a club's chances outweighed its opponents', or the other way round.
- xPts
- Expected points: the points a club's match-by-match xG would be worth on average. Each match's two xG figures become chances of a win, a draw and a loss, and a win is worth 3 and a draw 1.
- Pts vs xPts
- Actual points minus expected points based on match xG. Positive, drawn in green, is more points than the chances were worth on average; negative, in red, is fewer. It measures the gap and says nothing about its cause.
- npxG
- Non-penalty xG: xG with penalties removed, offered where the competition's figures support it. It changes xG, xGA and xGD; xPts is always worked out from all xG.
Expected points are read off the same score matrix that prices the board: each played match's two xG totals are taken as scoring rates, and the team's share is 3 × P(win) + 1 × P(draw), summed over the season. Understat arrives at the same figure by simulating each shot, which needs per-shot data, held here for %{competitions}. Passes per defensive action and deep completions are not shown because no source here ingests the event data behind them.