Premier League · 2024

FC Spartak Moscow 0–3 FK Krasnodar · Premier League

0–3Historical match

A completed match from a finished season. This page is the record of what happened.

Match at a glance

FK Krasnodar won 0–3.

Shots
1416
Shots on target
44
Expected goals
0.991.86
Possession
58%42%

Full time

What the match recorded

FK Krasnodar beat FC Spartak Moscow 3–0. Recorded in this match (FC Spartak Moscow – FK Krasnodar): shots 14–16, shots on target 4–4, expected goals 0.99–1.86, possession 58%–42%. This is what was recorded. It is not a claim that the result was foreseeable.

Pre-match record

What the data showed before kick-off. Kept for reference; it did not know the result.

FK Krasnodar's recent record differs from the season

moderate

FK Krasnodar's last-five goals scored average is above their season average.

3.2 goals/match ▲Goals forLast 5 · Season2.08 goals/match
Evidence and caveat

Comparison: An unweighted last-five average is compared with the unweighted season average.

Window: last_5 versus season

MetricLast 5SeasonBaseline
Goals for3.2 goals/match2.08 goals/match1.22 goals/match

Caveat: Five matches are sensitive to opponent mix and isolated match states.

The teams have contrasting possession records

moderate

FC Spartak Moscow have recorded the higher season possession share.

64.9% ●PossessionFC Spartak Moscow · FK Krasnodar54.8%
Evidence and caveat

Comparison: The recorded possession gap is 10.1 percentage points.

Window: season

MetricFC Spartak MoscowFK KrasnodarBaseline
Possession64.9%54.8%50.2%

Caveat: Possession share does not show where possession occurred or how chances were created.

This match

Match statistics

  • Shots14 shots16 shotsFC Spartak Moscow 14 shots, FK Krasnodar 16 shots
  • Shots on target4 shots4 shotsFC Spartak Moscow 4 shots, FK Krasnodar 4 shots
  • Expected goals0.99 xG1.86 xGFC Spartak Moscow 0.99 xG, FK Krasnodar 1.86 xG
  • Possession58%42%FC Spartak Moscow 58%, FK Krasnodar 42%
  • Corners4 corners2 cornersFC Spartak Moscow 4 corners, FK Krasnodar 2 corners
  • Fouls16 fouls9 foulsFC Spartak Moscow 16 fouls, FK Krasnodar 9 fouls

History

Head-to-head

Recent meetings between these teams.

Last 5 meetings

3FC Spartak Moscow
0Draws
1FK Krasnodar
FC Spartak Moscow — FK Krasnodar · Premier League1–0
FK Krasnodar — FC Spartak Moscow · Premier League2–0
FC Spartak Moscow — FK Krasnodar · Premier League4–3
FK Krasnodar — FC Spartak Moscow · Premier League1–4

Head-to-Head & Recent Meetings

Metric comparison

Team comparison

Season averages, with the sample size beside each metric.

Where the edge is

Season: FC Spartak Moscow favored in 4 of 11 directional metrics · FK Krasnodar in 7

led this metric higher value (descriptive) too close

Window

Season

FC Spartak Moscow12 matchesFK Krasnodar12 matches
1.42 goals/matchGoals scored12/12▲ 2.08 goals/match
1 goal/matchGoals allowed12/12▲ 0.42 goals/match
1.62 xG/matchExpected goals8/10▲ 2.18 xG/match
15.5 shots/matchShots8/10▲ 17.4 shots/match
4.5 shots/matchShots on target8/10▲ 5.7 shots/match
64.9% ●Possession8/1054.8%
5.88 corners/match ●Corners8/104.7 corners/match
14.3 fouls/matchFouls8/1010.5 fouls/match

Evidence quality

How much supports this analysis

Grade B · Useful evidenceUseful evidence — limited
Season samples12 / 12home / away teams
Recent samples5 / 5last-five windows
FreshnessLess than one dayfrom nearest prior match
  • Evidence is usable but does not meet the strongest completeness threshold.

Known unknowns

  • Lineups, injuries, suspensions and tactical changes are not available in the retained dataset.
  • Some metrics are unavailable or below their observation minimum: cards.
  • The fixture season differs from the competition's configured active season.
Analysis cutoff: Sat, 19 Oct 2024, 17:30 UTC · analysis-v4

Team rankings in Premier League

Make a graphic from this match

Creator Studio builds a branded post from this match's recorded data, with its evidence grade and source cutoff carried into the export.

Turn this match into a graphicReady-made from PitchMath data · No sign-up required