Spartak Moscow produced a ruthless away performance to beat Lokomotiv Moscow 4-0 in the Russian Premier League on 2 November 2026, turning a fiercely contested capital derby into a one-sided statement win at RZD Arena.

Match overview

Spartak were sharper from the opening whistle and punished Lokomotiv with a clinical display of counter-attacking football. The visitors scored four unanswered goals, kept a clean sheet, and underlined their credentials as one of the most dangerous sides in the Russian Premier League on the break. Lokomotiv had spells of possession but struggled to turn territory into clear chances, and the scoreline became increasingly difficult to recover from once Spartak added a second goal before half-time.

Derbies between these two Moscow clubs are rarely short of intensity, but this one swung decisively in Spartak’s favour. Their pressing forced errors, their midfield won the second balls, and their forward line repeatedly exposed space behind Lokomotiv’s advanced full-backs. For Lokomotiv, it was a painful home defeat against their biggest rivals; for Spartak, it was a result that will be remembered for its control and efficiency.

Key moments

• Early breakthrough: Spartak’s high press forced a turnover in Lokomotiv’s half, and the opener arrived inside the first 20 minutes to settle the visitors.
• Half-time cushion: A second goal on the stroke of half-time gave Spartak a commanding lead and changed Lokomotiv’s half-time team talk.
• Kill-off goal: Early in the second half, Spartak won the ball in midfield and broke quickly for a third, effectively ending the contest.
• Late fourth: A fourth goal in the closing stages capped a counter-attacking masterclass and completed a miserable evening for the hosts.

Tactical story

Spartak set up to absorb pressure and strike in transition, and the plan worked almost perfectly. Their midfield stayed compact, denied Lokomotiv easy access between the lines, and then released wide runners into the channels whenever possession was regained. Lokomotiv’s build-up was patient but predictable, and too often their final pass arrived after Spartak had already recovered their shape.

The away side’s ability to win duels in the middle third was a major factor. Spartak’s central defenders stepped out aggressively when needed, while the holding midfielders screened the space in front of the back four. Lokomotiv tried to switch play and use the flanks, but Spartak’s wide players tracked back diligently and turned defence into attack with direct running. By the time Lokomotiv pushed more bodies forward in the second half, Spartak had the perfect platform to counter and punish the gaps.

Standout performers

Spartak’s goalkeeper deserved credit for a composed clean-sheet performance, even though the defensive unit in front of him limited Lokomotiv to mostly speculative efforts. The centre-back pairing won the key aerial duels and stepped into midfield to break up attacks, while the engine room set the tempo with sharp passing and intelligent positioning. Further forward, Spartak’s wide attackers caused constant problems with their pace and willingness to run beyond the last defender.

For Lokomotiv, there were few positives beyond brief spells of possession. Their goalkeeper made several saves to prevent the scoreline from becoming even heavier, and one or two midfielders tried to drive the team forward, but the home side lacked the cutting edge needed to make the derby competitive.

Season impact

The three points strengthen Spartak’s position in the Russian Premier League standings and give them significant momentum in the race for the top places. A 4-0 derby win away from home does more than add points — it sends a message to rivals about Spartak’s quality and ruthlessness. For Lokomotiv, the defeat raises immediate questions about their home form and their ability to handle high-intensity pressing.

With the result, Spartak also claim bragging rights in one of Russian football’s most heated rivalries. Lokomotiv must regroup quickly, because a heavy derby loss can linger if the next performance does not bring a response.