T20 betting glossary

The vocabulary of T20 cricket statistics, defined plainly — and every term shown with a real number from the ball-by-ball data rather than a made-up illustration.

Venue and pitch

Where a match is played changes what a score is worth. These are the numbers that tell you by how much.

Par score

The first-innings total that wins about as often as it loses at a particular ground.

Par is the score that makes a contest even at that specific ground. Every par figure on this site is the median first-innings total there — a median rather than a mean, so a single 240 does not drag it upwards and misrepresent a typical night. Where a page shows a mean instead, it says so and calls it an average.

Par is the most useful single number in T20 betting because it turns a scoreboard into a probability. A first-innings 160 is a commanding total at one ground and 25 short at another, and until you know which, the number on the screen tells you very little.

In the data

Across the 143 grounds with enough T20 cricket to publish, the median par score is 154. The spread is wide: Rawalpindi Cricket Stadium sits at 187 from 48 T20s, while Botswana Cricket Association Oval 1 sits at 104. The same 165 is a poor total at one and a match-winning one at the other.

Rawalpindi Cricket Stadium venue stats

Chase win percentage

How often the team batting second wins at a ground.

The share of completed matches at a ground won by the side chasing. Fifty percent is a neutral ground; anything much above or below tells you the venue itself is applying a thumb to the scale.

The common mistake is assuming a high-scoring ground is a good ground to chase at. Those are separate properties and they come apart often.

In the data

Holkar Cricket Stadium is the most chase-friendly ground in the database at 75%, against 33% at Headingley. Headingley makes the point about the two properties coming apart: it is among the highest-scoring grounds here, at a par of 182, and still the hardest place in the database to chase.

Headingley venue stats

Toss bias

Whether winning the toss at a ground confers a real advantage, and which choice captains make with it.

Two separate questions live inside the toss. What do captains choose here — bat first or field first? And does the side that won the toss actually go on to win more often than not?

They are worth separating because captains follow convention, and convention is often behind the data. A ground where nine captains in ten field first, and the chasing side still loses more than it wins, is one where the received wisdom has stopped matching the pitch.

In the data

Every venue page carries the toss split alongside the chase record: what captains chose, and how each choice worked out. Shere Bangla National Stadium has the deepest sample in the database at 328 T20s.

Shere Bangla National Stadium toss and chase splits

Powerplay

The first six overs of an innings, when only two fielders may stand outside the thirty-yard circle.

The fielding restriction makes these the easiest overs to score in and the most dangerous to bat in, because the same gaps that reward a boundary reward a catch. Powerplay scoring rates and wickets vary more between grounds than any other phase.

For betting, the powerplay matters out of proportion to its six overs: it sets the platform that the rest of the innings either builds on or spends recovering from.

In the data

Every venue page publishes the powerplay as its own block: average runs and wickets in the first six, first innings and second. At Shere Bangla National Stadium a first innings averages 41.7 runs in those six.

Shere Bangla National Stadium powerplay stats

Middle overs

Overs seven to fifteen, when the field spreads and spin usually operates.

With the circle restriction lifted, scoring slows and the contest becomes one of accumulation against control. This is where spin bowls most of its overs and where matches are quietly decided more often than the highlights suggest.

A ground that suppresses the middle overs will produce lower totals than its powerplay numbers imply.

In the data

Venue pages split a first innings three ways, and the three add up to the whole innings. At Shere Bangla National Stadium, the deepest sample in the database at 328 T20s, it averages 41.7 in the powerplay, 63.3 through overs seven to fifteen and 45.4 at the death. Nine overs against the powerplay's six is why the middle carries the largest share of a total at almost every ground, and why a ground that suppresses it is hard to make runs at.

Shere Bangla National Stadium phase breakdown

Death overs

The last five overs, when batters accept high risk for a high rate.

From over sixteen the calculation changes: a wicket costs less than a dot ball, so the scoring rate rises sharply and so does the wicket rate. Death bowling is the most specialised skill in the format and the most variable between grounds.

Small boundaries and true bounce inflate death scoring; larger square boundaries and grip suppress it. Death hitting is most of the distance between a ground's par score and its highest totals, which is why the spread between grounds matters more here than in any other phase.

In the data

Every venue page publishes the death block alongside its run rate. The spread between grounds is the widest of any phase: a first innings at Rawalpindi Cricket Stadium averages 54.1 runs in overs sixteen to twenty, against 30.4 at Entebbe Cricket Oval — 24 runs of difference from the last five overs alone. Both count only the innings that got there, so an innings bowled out in the fifteenth does not drag the average down.

Rawalpindi Cricket Stadium death overs stats

Dew

Evening moisture that wets the ball, removes grip and makes a chase measurably easier.

In night matches at humid venues, dew settles during the second innings. A wet ball is harder to grip, so spin turns less and seam swings less, and the ball comes onto the bat more predictably. Captains at dew-affected grounds field first almost automatically.

This site does not measure dew directly — there is no ball-by-ball record of it. What it does measure is the consequence. Where dew genuinely matters, it shows up as a chase win percentage well above fifty, so the chase number is the honest proxy and the one to trust.

In the data

Rather than an unmeasured dew rating, read the chase record: Holkar Cricket Stadium at 75% is what a genuine second-innings advantage looks like in the data.

Holkar Cricket Stadium chase record

Batting

T20 rewards rate over accumulation, which changes what the traditional batting numbers are worth.

Strike rate

Runs scored per 100 balls faced.

Runs divided by balls faced, multiplied by 100. A strike rate of 150 means fifty percent more runs than balls. In T20 it is the primary batting measure, ahead of average, because the scarce resource is deliveries rather than wickets.

Wides are not counted as balls faced, matching standard scoring practice, so they do not depress a batter's strike rate.

In the data

Chris Gayle has scored 177 runs from 206 balls against Sunil Narine, a strike rate of 86. It is the largest batter-bowler sample in the database, and it sits well under the median of 123 across all 1,261 published pairings.

Chris Gayle v Sunil Narine

Batting average

Runs scored per dismissal.

Runs divided by the number of times out. It remains a useful measure of how reliably a batter survives, but it carries far less weight in T20 than in longer formats.

The reason is that a T20 innings is limited by balls, not by wickets. A batter averaging 40 at a strike rate of 110 may cost their side more than one averaging 25 at 160. Read the two together or not at all.

In the data

Across the same 206 balls, Sunil Narine has dismissed Chris Gayle 6 times, once every 34 balls — a good illustration of why survival and scoring rate have to be read together.

Chris Gayle v Sunil Narine

Boundary percentage

The share of balls faced that a batter hits for four or six.

Boundaries supply the majority of runs in T20, so the rate at which a batter finds them is closer to the heart of their value than their average is. A boundary percentage above twenty is high.

It is also the number that travels worst between grounds. A batter's boundary rate at a small ground says relatively little about what they will do at a large one, which is why venue splits matter.

In the data

Chris Gayle has found the boundary off 11% of the balls Sunil Narine has bowled to him, against a median of 16% across every published pairing. Suppressing the boundary is most of what a containing bowler does.

Chris Gayle v Sunil Narine

Dot ball percentage

The share of balls that produce no run.

A dot ball is the bowler's real currency. In a twenty-over innings the batting side faces around 120 deliveries, so every dot removes close to one percent of the innings while conceding nothing.

Dot percentage is the most reliable single indicator of bowling control, and it predicts economy better than wickets do — a bowler can take wickets in an expensive spell, but a bowler cannot bowl dots in one.

In the data

59% of the 206 balls Sunil Narine has bowled to Chris Gayle have been dots. That, more than the wickets, is what has kept the strike rate at 86.

Chris Gayle v Sunil Narine

Impact player

An IPL rule allowing a team to substitute one player for another during a match.

Introduced in the IPL in 2023. Each side names four substitutes and may bring one on at set points, replacing a player who takes no further part. In practice it lets a team field an extra specialist batter when chasing or an extra bowler when defending.

Its betting relevance is that it inflates scoring. Batting sides can bat deeper without weakening the bowling attack, so first-innings totals in competitions using the rule run above what the same grounds produced before it. Be careful comparing a venue's recent IPL scores against its longer history for that reason.

The rule is specific to the IPL and to competitions that have copied it. It does not apply in most T20 cricket.

In the data

Player records on this site cover every competition a player has appeared in, so an IPL-inflated season sits alongside the rest of their career rather than standing in for it.

Player records

Bowling

Three measures, each answering a different question about the same spell.

Economy rate

Runs conceded per over.

Runs conceded divided by overs bowled. In T20 an economy under seven is excellent, eight is respectable and ten is expensive — figures that would look alarming in a fifty-over match and unthinkable in a Test.

Economy is the most important bowling number in the format, because a bowler's four overs are a fixed cost and the only question is what the batting side gets for them.

In the data

Venue pages list the leading wicket-takers at each ground with their economy there, which is usually a better guide than a bowler's overall figure.

Shere Bangla National Stadium leading bowlers

Bowling average

Runs conceded per wicket taken.

Runs conceded divided by wickets taken. Lower is better. It blends two things — how expensive a bowler is and how often they strike — which makes it a reasonable summary and a poor diagnostic.

On this site a bowler is credited only with the wickets that are genuinely theirs. Run outs, obstruction and retirements are dismissals but not the bowler's, and they are excluded. That is a common source of disagreement between statistics providers.

In the data

Sunil Narine has conceded 177 runs and taken 6 wickets in this pairing alone.

Chris Gayle v Sunil Narine

Bowling strike rate

Balls bowled per wicket taken.

How often a bowler strikes, independent of cost. A strike rate of 18 means a wicket every three overs.

It matters most for bowlers used in the powerplay and at the death, where taking a wicket changes what the batting side can attempt next over. A containing bowler and a striking bowler can share an economy rate and do entirely different jobs.

In the data

In this pairing Sunil Narine has struck once every 34 balls — the balls-per-dismissal figure shown on every matchup page.

Chris Gayle v Sunil Narine

Matchups and markets

Where the individual numbers meet a specific contest, and where sample size starts to matter more than anything else.

Head-to-head matchup

The record between one batter and one bowler across every competition they have met in.

Every ball is recorded with both the batter and the bowler, so the record between any two players can be reconstructed: runs, balls, dismissals, dots and boundaries, across every league they have both played in rather than just the current one.

This is the least-served useful statistic in cricket. Scorecards are everywhere; the aggregate of two players' meetings has to be computed from every delivery, so almost nobody publishes it.

Treat it as evidence rather than proof. A bowler who has dismissed a batter four times in sixty balls has told you something real, but sixty balls is still sixty balls.

In the data

Chris Gayle against Sunil Narine is the most-observed pairing here: 177 runs from 206 balls, out 6 times, 59% dots.

Chris Gayle v Sunil Narine

Runs line

A bookmaker's over/under total, for an innings, a match or an individual player.

A line is a number you bet above or below rather than a result you bet on: a first-innings total of 168.5, a match aggregate, a player's runs in a game. The half-run exists to prevent a tie.

Lines for a fixture start from what the venue typically produces and are adjusted for the sides, the conditions and the money already taken. A venue's par score and phase splits are the same starting point, which is what makes them worth knowing before the line appears.

In the data

The reason two fixtures carry very different lines is mostly the ground beneath them: par at Rawalpindi Cricket Stadium is 187, against 104 at Botswana Cricket Association Oval 1.

All venue statistics

Sample size

How much cricket a number is built on, and therefore how much weight it can carry.

T20 is a short format and its statistics move violently in small samples. Three dismissals in twenty balls looks like domination and is very often noise; a batting average from six innings is close to meaningless.

This is the reason for the thresholds on this site rather than an apology for them. A venue needs at least 20 T20 matches, a player 20 appearances and a batter-bowler pairing 60 balls before it gets a page of its own. Below that the numbers change too much from one innings to the next to support a conclusion.

When a number does surprise you, check what it is built on before acting on it. That is the single habit that separates a useful statistic from a misleading one.

In the data

342,567 batter-bowler pairings have met at least once in this database. Only 1,261 have met for 60 balls or more, which is the point at which the record starts to be worth reading.

Browse matchups

Every figure on this page is computed from ball-by-ball data and refreshes with it — the examples are not fixed illustrations. More on where the data comes from and how it is counted on the about page.