🎯

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

📰

Prediction vindicated as Barnsley edge out Blackpool 2-1.

📝 Match Report

How It Unfolded

Barnsley beat Blackpool 2-1 at Oakwell, Regular Season - 27, in the League One. 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 Barnsley 1.82 xG and Blackpool 1.41 xG, a combined 3.24. The scoreboard read 2-1 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 Barnsley attack 1.19 / defence 1.31 against Blackpool attack 0.98 / defence 1.13, drawn from 67/71 games (CurrentSeason).

On the result, the model split it Barnsley 47% | Draw 23% | Blackpool 30%, with Barnsley to win its most likely call at 47%. The scoreboard confirmed the model's leading pick.

Goals & Markets

The model rated Over 2.5 goals at 63%. The game delivered 3, so it went over — the model's lean was correct. Over 1.5 had been 83% and landed. Over 3.5 was 41% and did not. On both teams to score, the model sat at 63% and the match saw both sides score — another call in the model's favour. Historically the two sides average 61% Over 2.5 across their same-competition games (Barnsley 66%, Blackpool 57%), a base rate that agreed with today's over. Their combined BTTS history runs at 62%, which matched the both-scored outcome.

Trading Patterns vs Reality

Barnsley's trading profile (67 games, 33 home) set some clear expectations: BTTS lands in 67% of their matches — today it did.

Blackpool's trading profile (67 games, 33 away) set some clear expectations: BTTS lands in 57% of their matches — today it did.

Form vs Result

The form lines were close — Barnsley 1.34 PPG, Blackpool 1.40 PPG — offering no strong steer, and the Barnsley win broke the near-deadlock.

Verdict

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

💡 Key Insights