ABF vs BT Live Match Intelligence

Live

Back To Live Match

Public model signal

BT

Chasing side is still within the model's scoring range.

72%

Score23-0

Overs2.3 overs

Expected finalExpected final 177

BattingBT

BowlingABF

CRRCRR 9.20

RRRRRR 7.60

ResourcesResources 92.2%

Resource WPResource WP 81%

Par paceScore vs par pace 3.6

PressurePressure 7.60

How these metrics are calculated

CRR: current runs divided by completed overs. RRR: runs still required divided by overs remaining.
Expected final: resource-calculator estimate for the completed innings. Projected score: current-rate extrapolation.
Venue average: full-innings venue scoring baseline. Score vs par: current score minus resource-adjusted par.
Resources: model-calculated resources remaining. Resource WP: the structural win probability from that resource state.
Model probability: calibrated public win probability from the selected gender-aware T20 or ODI model.

Sources: the public-safe prediction payload and the match snapshot. Raw training features are not exposed.

Win Probability

Current model probability

BT 72%ABF 28%

The probability line shows how the model view changed during the match, keeping the first-innings batting side as the same reference across both innings.

19.4Innings 22.3

Model probability by update 50% balance

Open prediction update log (21 updates)

Inn 1 · 19.4153/564%Expected 156

Inn 1 · 19.5153/559%Expected 155

Inn 1 · 20.0155/563%Expected 155

Inn 2 · 20.0155/50%Expected 155

Inn 2 · Update0/066%Expected 160

Inn 2 · 0.10/065%Expected 159

Inn 2 · 0.26/071%Expected 167

Inn 2 · 0.310/074%Expected 172

Inn 2 · 0.411/074%Expected 172

Inn 2 · 0.512/073%Expected 173

Inn 2 · 1.012/072%Expected 171

Inn 2 · 1.112/071%Expected 170

Inn 2 · 1.212/069%Expected 169

Inn 2 · 1.318/075%Expected 177

Inn 2 · 1.316/073%Expected 174

Inn 2 · 1.417/072%Expected 174

Inn 2 · 1.523/077%Expected 182

Inn 2 · 2.023/076%Expected 181

Inn 2 · 2.123/075%Expected 180

Inn 2 · 2.223/074%Expected 178

Inn 2 · 2.323/073%Expected 177

Expected finish

Expected final versus venue

Expected final comes from the model resource calculator; venue average is the full-innings venue scoring baseline.

Expected finalExpected final 177

Venue averageVenue average 154.0

Resource and pace

What the innings has left

Par pace compares current score with resource-adjusted par. CRR is runs per over; RRR is the required chase rate.

Resources remainingResources 92.2%

CRR / RRRCRR 9.20 · RRR 7.60

Pressure

Why the state feels difficult

The model sees measurable pressure against the current resource position.

Momentum

How the match is moving

Recent updates have moved toward the batting side. The timeline shows the direction rather than a certainty.

Confidence

How strongly to read the signal

The current model lean is pronounced, while the timeline and freshness label show why it should not be read as certainty.

Model factors

Why the signal leans this way

Expected final 177, 23 above the venue average.
Current score is 3.6 runs above resource-adjusted par.
Chase pressure is 7.6 required runs per over from here.

These are public-safe factors from the current match state; raw training features remain private.

Match briefing

Context beyond the score

Venue behaviourTracking above the venue baseline.

Toss impactToss impact will appear when toss context is available.

Expected score177

Turning point1.5 · 23/0 · +5%

Latest swing74% to 73%

This public briefing reuses the explanation-pack pattern from the intelligence/video workflow. Player picks, market replay, and operator-only fields stay excluded.

Win probability

BT

72%

Chasing side is still within the model's scoring range.

What changed

Latest visible shift

+5%

Why it changed

Current explanation

Expected final 177, 23 above the venue average.

What matters next

Next watchpoint

Use this route for deeper probability and match-state interpretation while keeping the canonical match page as the score-first live entry point.

Keep the signal

Get probability updates

Follow the match from score context to model change without losing the live match page.