Skip to content

Porto vs Manchester City — market analysis & odds

Final score: 0–2

Final score: Porto 0–2 Manchester City. Pre-match, Clauseground's combined estimate was Porto 19%, the draw 24%, Manchester City 58%. Manchester City won — an outcome we carried at 58%. That was the combined estimate's most likely single result.

Updated · overall, market, and model views are labeled separately

Expert analysisFull detail remains available

Pre-match model vs market

Market and model are independent views, not competing answers. Their difference is shown in percentage points (pp) and is a prompt to investigate assumptions or missing information.

Portomodel 19% · market —
Drawmodel 24% · market —
Manchester Citymodel 58% · market —

Market = probability from the designated reference market after bookmaker margin is removed. Model = independent Dixon-Coles-adjusted simulation. The Quick read uses the separately labeled overall estimate, which combines these inputs.

Evidence and inputs

  • Monte Carlo simulation: 50,000 runs (engine v1.1-dc-poisson-mktshares).
  • Rest: Porto 7d, Manchester City 3d since last match.
  • League scoring baseline: 2.9 goals/game.
  • Home advantage applied for Porto.
  • Lineups unconfirmed at last model run.

Questions

Who won Porto vs Manchester City?

Manchester City won: the final score was Porto 0–2 Manchester City. Clauseground's pre-match blend carried that outcome at 58%. That probability described uncertainty; it did not promise the result.

How does Clauseground predict Porto vs Manchester City?

Clauseground uses an independent Poisson model with a Dixon-Coles low-score correction and removes the margin from a complete designated reference market. It shows the model and market views separately, then may calculate a market-specific combined estimate. Each probability retains its source label and timestamp.

Decision support, not betting advice. No guaranteed outcomes. 18+/21+ where applicable. Gamble responsibly.

Probabilities are labeled by source — market, model, or combined. How the model works →