🎯

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

📰

Monaco cruise to a comfortable 2-0 victory over Angers.

📝 Match Report

How It Unfolded

Monaco beat Angers 2-0 at Stade Louis II, Regular Season - 24, in the Ligue 1. 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 Monaco 1.66 xG and Angers 0.91 xG, a combined 2.57. The scoreboard read 2-0 for 2 actual goals. Angers landed 0.9 under their projected return. Those figures were built on strength ratings of Monaco attack 1.20 / defence 1.12 against Angers attack 0.67 / defence 0.92, drawn from 57/57 games (CurrentSeason).

On the result, the model split it Monaco 55% | Draw 24% | Angers 21%, with Monaco to win its most likely call at 55%. The scoreboard confirmed the model's leading pick.

Goals & Markets

The model rated Over 2.5 goals at 47%. The game delivered 2, so it stayed under — the model's lean was correct. Over 1.5 had been 73% and landed. On both teams to score, the model sat at 48% and the match did not — another call in the model's favour. Historically the two sides average 46% Over 2.5 across their same-competition games (Monaco 63%, Angers 30%), a base rate that agreed with today's under. Their combined BTTS history runs at 49%, which matched the one-sided outcome.

Trading Patterns vs Reality

Monaco's trading profile (57 games, 28 home) set some clear expectations: BTTS lands in 61% of their matches — today it did not.

Angers's trading profile (57 games, 28 away) set some clear expectations: BTTS lands in 37% of their matches — today it did not; they fail to score in 39% of games, a blank that repeated today.

Form vs Result

On form, Monaco arrived the stronger side — 1.67 PPG against 1.14. The form guide was vindicated by the result. Monaco (home/away splits) conceded 0 against a 1.25 average — tighter than their form line.

Verdict

Grading the result against the stored data, 4 of 4 pre-match signals came in: result (hit), Over 2.5 (hit), BTTS (hit), form (hit). The data earned its keep here, calling the bulk of the fixture correctly.

💡 Key Insights