🎯

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

📰

Prediction vindicated as Lazio edge out Lecce 1-2.

📝 Match Report

How It Unfolded

Lazio beat Lecce 1-2 at Stadio Ettore Giardiniero - Via del Mare, Regular Season - 17, in the Serie A. 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 Lecce 1.19 xG and Lazio 1.65 xG, a combined 2.84. The scoreboard read 1-2 for 3 actual goals. Both sides finished within a goal of their individual projections, so the scoreline sat close to the model's expected shape. Those figures were built on strength ratings of Lecce attack 0.90 / defence 1.14 against Lazio attack 1.08 / defence 1.01, drawn from 54/54 games (CurrentSeason).

On the result, the model split it Lecce 28% | Draw 24% | Lazio 48%, with Lazio to win its most likely call at 48%. The scoreboard confirmed the model's leading pick.

Goals & Markets

The model rated Over 2.5 goals at 54%. The game delivered 3, so it went over — the model's lean was correct. Over 1.5 had been 78% and landed. On both teams to score, the model sat at 56% and the match saw both sides score — another call in the model's favour. Historically the two sides average 44% Over 2.5 across their same-competition games (Lecce 37%, Lazio 52%), a base rate that pointed the other way from today's over. Their combined BTTS history runs at 47%, which did not match the both-scored outcome.

Trading Patterns vs Reality

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

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

Form vs Result

On form, Lazio arrived the stronger side — 1.70 PPG against 1.00. The form guide was vindicated by the result.

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