🎯

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

📰

Rubin and Akron share the spoils in a 1-1 draw.

📝 Match Report

How It Unfolded

Rubin and Akron finished level at 1-1 at Ak Bars Arena, Regular Season - 25, in the Premier League. With the result on the board, the sections below measure it against everything the model and the numbers projected in advance.

The Model vs The Result

The Poisson model went into this projecting Rubin 1.99 xG and Akron 0.84 xG, a combined 2.83. The scoreboard read 1-1 for 2 actual goals. Rubin fell 1.0 short of their projected output. Those figures were built on strength ratings of Rubin attack 0.95 / defence 0.74 against Akron attack 1.04 / defence 1.41, drawn from 54/54 games (CurrentSeason).

On the result, the model split it Rubin 64% | Draw 21% | Akron 15%, with Rubin to win its most likely call at 64%. Instead the game produced a draw, an outcome the model had rated at just 21% — a clear break from expectation and a genuine upset by the numbers.

Goals & Markets

The model rated Over 2.5 goals at 54%. The game delivered 2, so it stayed under — the opposite of the projected direction. Over 1.5 had been 77% and landed. On both teams to score, the model sat at 49% and the match saw both sides score — a miss on BTTS. Historically the two sides average 54% Over 2.5 across their same-competition games (Rubin 48%, Akron 59%), a base rate that pointed the other way from today's under. Their combined BTTS history runs at 52%, which matched the both-scored outcome.

Trading Patterns vs Reality

Rubin's trading profile (54 games, 27 home) set some clear expectations: BTTS lands in 44% of their matches — today it did; they keep a clean sheet 33% of the time, and conceded here.

Akron's trading profile (54 games, 27 away) set some clear expectations: BTTS lands in 59% of their matches — today it did.

Form vs Result

The form lines were close — Rubin 1.46 PPG, Akron 1.06 PPG — offering no strong steer, and the draw fit that even billing.

Verdict

Grading the result against the stored data, 0 of 3 pre-match signals came in: result (miss), Over 2.5 (miss), BTTS (miss). The data was on the wrong side of this result more often than not — a reminder that a single match sits well inside the model's variance.

💡 Key Insights