Changchun YaTai vs Cangzhou Mighty Lions Prediction — Model Probabilities
Edge (pp): green = we see more probability than the market · gold = essentially even (±0.5pp) · red = we see less. The Decision above outranks any single row: the engine backs well-supported edges, not merely big ones.
Changchun YaTai v Cangzhou Mighty Lions — Team-Based Signals
Changchun YaTai vs Cangzhou Mighty Lions Head-to-Head — Last 5 Meetings
3-1
HT 1-0
Cangzhou Mighty Lions
ÇİN
2-4
HT 0-1
Changchun YaTai
ÇİN
0-2
HT 0-1
Cangzhou Mighty Lions
ÇİN
1-2
HT 0-1
Changchun YaTai
ÇİN
Changchun YaTai 1-0 Cangzhou Mighty Lions — Actual Match Statistics
Changchun YaTai nicked a narrow win over Cangzhou Mighty Lions 1-0. The game was level at 0-0 at the break, so the decisive goals came after it.
Just as the model leaned, our model had Changchun YaTai as the likeliest winner at 53%, and the 1-0 landed on that lead. The goals read — over 2.5 goals (59%), both teams to score (57%) — went the other way, though.
On the day, Changchun YaTai had 50% of the ball to Cangzhou Mighty Lions's 50%, shots finished 20-5, expected goals 2.01 to 0.29 — an xG gap that size says the one-goal margin undersold Changchun YaTai's control.
For context: across their last 5 meetings in our records, Changchun YaTai had the better of it with 3 wins. Those games averaged 1.80 goals for Changchun YaTai and 1.60 for Cangzhou Mighty Lions.
What was the final score of Changchun YaTai vs Cangzhou Mighty Lions?
Changchun YaTai 1-0 Cangzhou Mighty Lions in the China Halk Cumhuriyeti - Super League on 27/07/2024. The analysis above shows what our model predicted before kick-off next to what actually happened.
What did the model predict for Changchun YaTai vs Cangzhou Mighty Lions?
Before kick-off our model rated a Changchun YaTai win the most likely single outcome at about 53%, with the full match-result split Changchun YaTai 53%, draw 23%, Cangzhou Mighty Lions 24%. The final score 1-0 confirmed our model's pre-match leads on Match Result (Changchun YaTai) — while Over 2.5, BTTS Yes went the other way.