🎯

Fixture360 only lists fixtures from a curated set of leagues, chosen specifically to keep our prediction model accurate.

📰

Prediction vindicated as Rubin edge out Lokomotiv 1-0.

📝 Match Report

How It Unfolded

Rubin beat Lokomotiv 1-0 at Ak Bars Arena, Regular Season - 24, in the Premier League. That is the final score; the rest of this report grades it against what the data forecast beforehand.

The Model vs The Result

The Poisson model went into this projecting Rubin 1.92 xG and Lokomotiv 1.11 xG, a combined 3.03. The scoreboard read 1-0 for 1 actual goal. Rubin fell 0.9 short of their projected output. Lokomotiv landed 1.1 under their projected return. Those figures were built on strength ratings of Rubin attack 1.01 / defence 0.95 against Lokomotiv attack 1.07 / defence 1.28, drawn from 53/53 games (CurrentSeason).

On the result, the model split it Rubin 53% | Draw 28% | Lokomotiv 19%, with Rubin to win its most likely call at 53%. The scoreboard confirmed the model's leading pick.

Goals & Markets

The model rated Over 2.5 goals at 58%. The game delivered 1, so it stayed under — a miss for the goals model. Over 1.5 had been 84% and missed. On both teams to score, the model sat at 60% and the match did not — a miss on BTTS. Historically the two sides average 49% Over 2.5 across their same-competition games (Rubin 45%, Lokomotiv 53%), a base rate that agreed with today's under. Their combined BTTS history runs at 58%, which did not match the one-sided outcome.

Trading Patterns vs Reality

Rubin's trading profile (53 games, 26 home) set some clear expectations: BTTS lands in 49% of their matches — today it did not.

Lokomotiv's trading profile (53 games, 26 away) set some clear expectations: BTTS lands in 66% of their matches — today it did not.

Form vs Result

The form lines were close — Rubin 1.42 PPG, Lokomotiv 1.77 PPG — offering no strong steer, and the Rubin win broke the near-deadlock. Rubin (home/away splits) conceded 0 against a 1.35 average — tighter than their form line. Lokomotiv (home/away splits) managed 0 against a 1.81 scoring average — below par going forward.

Verdict

Grading the result against the stored data, 1 of 3 pre-match signals came in: result (hit), Over 2.5 (miss), BTTS (miss). A poor return for the projections: the match defied the majority of what the numbers expected.

💡 Key Insights