Every cricket site has a scorecard. 2for22 asks a
different question of every ball: what did it do to the
match? Here is what you will find on a match screen, tab by
tab, and how to read it.
Commentary the match as the model sees it, ball by ball
Two numbers sit above every live match: the batting side's chance of winning and the forecast score (in a chase, what is still needed and at what rate). Both are re-read after every ball and refresh on their own.
Every partnership so far, each with what it did to the forecast and the win chance — and the bowlers who bowled through it, with their runs, balls and wickets in that stand alone.
The last completed over, opened up: every batter who faced it, his balls and runs, and the win chance and forecast before and after the over. Step back through every earlier over.
England v Sri Lanka, 19 Sep 2026
Sri Lanka's second-wicket stand made 17 off 16 balls and still cost them:
forecast −9, win chance −7.5%.
Through it Dawson went for 9 off 6, Jacks 6 off 5 with the wicket, Baker 2 off 5.
A scorecard cannot tell you any of that.
Before a ball is bowled, 2for22 reads every batter against every bowler from years of T20 data: his record against that type of bowling in those overs, and the bowler's against that type of batter. Each pair comes out in the batter's favour, evenly matched or against him.
This page scores those calls against what happened. Every ball goes in the row its pair predicted; Expected is what a league-average batter would make off those balls, moved by the match-up; vs expected is the difference. A positive number means the batter won the match-up.
Tap a row's label to open the pairs behind it, then read them as Pairs, By batter or By bowler.
England v Sri Lanka, 19 Sep 2026
In England's chase, the match-ups read in the batter's favour went for
82 off 39 balls against 54 expected — +27.7.
One pair did most of it: Buttler against Malinga, 28 off 8 balls,
11 expected, +16.7. Sri Lanka's innings read the other way:
99 off 84 readable balls against 105 expected, −6.1.
Two charts per innings, one point per over: the projected total and the batting side's chance of winning above; the runs off every over with the run rate below — in a chase, the rate still needed too.
Beneath them a row per over: bowler, runs, score, and how the forecast and the win chance moved.
Spot the turning point on the chart, then tap that over: every batter who faced it and what he made of it, the partnership as it stood, the bowler's figures. The chart tells you when; the row tells you why.
England v Sri Lanka, 19 Sep 2026
Sri Lanka's second over went for 15 off Archer: forecast 164 → 179,
win chance +11.4 to 52%. The very next over, Baker's,
cost 2 runs and Udara's wicket: forecast back to 162, win chance
−13.1. Two overs, and the innings had turned.
Squads every player's record, and a few numbers you will not find elsewhere
Both squads in full, and the playing XI marked the moment it is named.
Each player's batting and bowling over his career or his last 3, 5 or 10 matches. Tap Detailed for the rest: balls per four and six, dot-ball percentage, slug rate, RAA.
RAA — runs above average — is what a player added to his team's score compared with an average player in the same situation: same over, same wickets in hand, same score. An average T20 side batting first makes about 165; score 200 and the team is 35 above average, and RAA says which batters those 35 runs belong to. A 60 off 60 with wickets in hand is usually below average; the same 60 with wickets tumbling can be well above it.
Slug rate is runs per scoring ball — the dots taken out. It separates the batter who scores off everything from the one who blocks and then hits. For a bowler it is the same the other way: what he goes for on the balls that are scored off.
The star beside a name adds him to your fantasy team, right here.
Two examples
Ishan Kishan's 70 off 47 won the Player of the Match award,
RAA +10. Heinrich Klaasen's 47 off 26 in the same chase was RAA
+21 — his partnership was the one that took the
projected score from behind the target to well past it.
And Jos Buttler, career: strike rate 143, a dot ball 37% of the time,
slug rate 2.3 — when he does score, it is more than a couple a ball.
The idea. A scorecard tells you
who scored what. RAA tells you whose runs actually moved the match.
It measures each player's contribution to the team's final score
against what an average player would have contributed in the same
situation — same over, same wickets in hand, same runs on the
board. It is not a replacement for runs and wickets; it answers the
question they cannot: how hard was the moment, and how well was it
handled?
A real example. Chasing, their
side was 56/2 after 7.4 overs with the projected score below the
target. Klaasen joined Kishan and the two added 75 in seven overs;
when Klaasen fell at 14.3 the score was 131/3 and the projection was
well past the target. Of those 75, Klaasen made the greater share at
the faster rate, so his match RAA (+21) is more than
double Kishan's (+10) — even though Kishan's 70
off 47 won the official Player of the Match.
Batting RAA. If an average T20
side batting first makes 165 and a team makes 200, the team is 35
runs above average, and its batters' individual RAAs add up to
exactly 35 — each man's slice of it.
Bowling RAA. The same the other
way: the bowling side gave up 35 above average, and its bowlers' RAAs
sum to −35. A batter who makes +5 off a bowler in an over hands
that bowler −5.
One scale for everyone. A
player's RAA is batting plus bowling, so a 50 off 30 and a 3 for 25
can be set against each other as numbers rather than opinions. It
accumulates over a series or a career; the squads page shows it
per innings, where a positive figure means a player
has consistently given more than an average player would have from
the situations he faced.
A winning margin in runs. Team
A 200, Team B 170: A's players sum to +30, B's to −30, and you
can see who contributed which slice of the result. A win by
“five wickets with six balls to spare” becomes a runs
margin too, so results batting second can be ranked.
Every player's name on 2for22 opens a popup with two radar charts: how he bats against each type of bowling (right- and left-arm pace, off-spin, left-arm orthodox, wrist spin), and how he bowls against right- and left-handers through the innings.
Choose the measure — strike rate, runs per wicket, slug rate, dot-ball percentage, balls per four and six, or RAA per ball. The grey shape is the league average.
Green is better than average, red worse — a player's strengths and weaknesses at a glance, the moment a spinner comes on.
Key match-ups who has the edge, before a ball is bowled
The board at the top counts each side's favourable match-ups. The side with more of them usually has the stronger chance — and once both XIs are named, the counts are like for like.
Beneath it, a row per batter and a column per phase — powerplay, middle overs, death — naming every opposing bowler with a real edge either way, coloured from the batter's side, where the record is long enough to say.
Play the captain: with two batters at the crease, read across their rows in the phase you are in and see who is a good — or a bad — choice to bowl the next over.
England v Sri Lanka, 19 Sep 2026
The board read England 134, Sri Lanka 29 — England ahead on the match-ups by 105.
England won by eight wickets with ten overs to spare.
Pre-match forecast 500 matches before the real one
Once both playing XIs are named, 2for22 simulates the match 500 times between those two elevens — ball by ball, in your browser — and shows how often each side won.
Watch the count climb, then read the verdict with its margin. Tap Run again for a fresh 500; inside a few points of 50–50 it says so rather than picking a side.
It reads the two teams and nothing else — it does not change as the match is played. The live win chance on the Commentary tab is the one that does.
For every match, a recommended fantasy XI across both sides, ranked on each man's last five matches (70%), his career (20%) and his record against these opponents (10%). Change it as you like — here or with the star on the squads page — until five minutes after the start.
As the match is played, your team's points against the recommended XI's and against the best XI in hindsight, refreshed with the score.
How the points are counted
Batting
1 a run; a four +4 and a six +6 on top
25 / 50 / 75 / 100: +4 / +8 / +12 / +16
Strike rate, from 10 balls: over 170 +6, over 150 +4, 130 or more +2; under 70 −2, under 60 −4, under 50 −6
A duck −2
Bowling
A wicket 30; bowled or lbw +8 more
3 / 4 / 5 wickets: +4 / +8 / +12; a maiden +8
Economy, from 2 overs: under 5 +6, under 6 +4; over 11 −4, over 12 −6
