Melbourne City vs Wellington Phoenix 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.
Melbourne City v Wellington Phoenix — Team-Based Signals
Melbourne City vs Wellington Phoenix Head-to-Head — Last 6 Meetings
1-0
HT 0-0
Melbourne City
AVUS
3-0
HT 1-0
Wellington Phoenix
AVUK
4-1
HT 1-0
Wellington Phoenix
AVUS
1-3
HT 1-1
Melbourne City
AVUS
2-2
HT 2-0
Wellington Phoenix
AVUS
1-2
HT 0-2
Wellington Phoenix
AVUK
Melbourne City 1-0 Wellington Phoenix — Actual Match Statistics
Melbourne City nicked a narrow win over Wellington Phoenix 1-0. The game was level at 0-0 at the break, so the decisive goals came after it.
We called this one close before kick-off — 38% / 26% / 36% — and on the day Melbourne City made the difference.
Over 2.5 goals sat near a coin-flip at 53% and both teams to score was close to even at 49%.
On the day, Melbourne City had 52% of the ball to Wellington Phoenix's 48%, shots finished 28-11, expected goals 2.54 to 1.12 — an xG gap that size says the one-goal margin undersold Melbourne City's control.
For context: across their last 6 meetings in our records, Melbourne City had the better of it with 3 wins, 1 drawn. Those games averaged 2.17 goals for Melbourne City and 1.17 for Wellington Phoenix.
What was the final score of Melbourne City vs Wellington Phoenix?
Melbourne City 1-0 Wellington Phoenix in the Australia - A-League on 09/03/2024. The analysis above shows what our model predicted before kick-off next to what actually happened.
What did the model predict for Melbourne City vs Wellington Phoenix?
Before kick-off our model rated a Melbourne City win the most likely single outcome at about 38%, with the full match-result split Melbourne City 38%, draw 26%, Wellington Phoenix 36%. The final score 1-0 confirmed our model's pre-match leads on Match Result (Melbourne City), BTTS No — while Over 2.5 went the other way.