India start a tour of New Zealand today, and by the time the 150th anniversary Test is played at the MCG in March, most top teams will have crossed at least one ocean. That's the cricket season in one sentence: a calendar that moves teams between very different conditions at a pace that shows up in the numbers.

This column reads the season rather than calling it. I look at which parts of the cricket season calendar distort team data, how analysts adjust for them, and where reliable numbers come from. A result means little until you know where, when and with whom it happened.

The 2026-27 cricket season calendar

Before any number, I map the season. The order of series matters as much as the series themselves: a team arriving straight from a five-Test tour is not the same team that arrives rested.

Two things stand out. Australia play ten Tests in about fourteen weeks: four at home against New Zealand, five in India and the anniversary Test. And there is no Ashes series this Australian summer, whatever your group chat says. The only England Test in Australia is the one-off match in March.

The calendar also explains why one table in Test cricket looks odd at first glance.

Why the Test table uses percentages

The World Test Championship runs in two-year cycles. In the 2025-27 cycle, nine teams each play six series, three at home and three away. A win is worth 12 points, a tie 6 and a draw 4. The top two meet in the final at The Oval on 9-13 June 2027.

Series lengths vary from two Tests to five, so raw points would reward teams that simply play more. The ICC ranks the table by the percentage of available points won instead. When you read the table mid-season, check how many matches each team has played. A team on a high percentage after four Tests is carrying more uncertainty than one on a slightly lower figure after twelve.

Percentages fix one distortion. Home advantage is a bigger one.

Measuring home advantage

Analysts usually measure home advantage in two ways. The first is the home win-loss ratio: Tests won at home divided by Tests lost at home. The second is the gap between a team's batting average and bowling average, compared at home and away. A team that bats 10 runs per wicket better than it bowls at home, and 5 worse away, has a home record you shouldn't project onto its tours.

The effect is large. An ESPNcricinfo analysis from 2016 found the home win-loss ratio for 2010-2016 was the highest for any decade since the 1870s. That figure is ten years old, so I treat it as a reason to check rather than a current number.

Conditions are part of the same story. Cricket Australia expects room for only one or two fast bowlers on spin-friendly pitches in India in January and February. A pace attack's numbers from a home summer in Perth and Adelaide tell you little about those Tests in Nagpur or Chennai. Split every average by country, then by venue if the sample allows.

Conditions decide who plays. Workload decides who's still fit to play.

Workloads and the fast-bowler problem

A packed calendar hits fast bowlers hardest, and there is research to show it. A 2009 study in the American Journal of Sports Medicine followed 129 pace bowlers over ten seasons. Bowlers who sent down more than 50 overs in a match faced 1.77 times the injury risk in the following 21 days.

Teams plan around it. Australia chose to rest their three senior quicks from the Pakistan and Bangladesh tours, and in May their coach called managing those bowlers "the biggest challenge". Ten Tests in fourteen weeks puts workload at the centre of selection, and that changes how you should read team data:

1. Track the XI, not the badge. Results with a team's first-choice attack and with its reserves are different samples.
2. Count overs in the previous three weeks. In the 2009 study, the extra risk showed up over the following 21 days.
3. Watch gaps between Tests. Three Tests in seventeen days and three Tests in five weeks are different series.
4. Mark format switches. White-ball cricket between Tests changes who's fresh and who's travelling.

None of this predicts a result. It tells you which numbers belong in the same comparison.

Where the numbers come from

A season read is only as good as its data, and I'm fussy about sources. For ball-by-ball data, Cricsheet publishes match files under an open licence that requires attribution, which makes it a good base for any model you want to share. ESPNcricinfo's Statsguru is the standard reference for career and team records. The ICC publishes the official Test Championship table and rankings, and the boards publish fixtures: Cricket Australia, the BCCI and New Zealand Cricket for most of what's in the table above.

Two habits save trouble. Write down the date you pulled a number, because tables change weekly. And keep the sample size next to every average; twelve innings is a hint, not a pattern.

That's the frame I'll use in columns this season: the calendar first, conditions second, the numbers third. This column is analysis, and I don't comment on where to bet. Sportsbooks are for adults 18 and over; if you use one, set a limit before the series starts.

FAQ

When is the World Test Championship final?

The 2025-27 final is scheduled for The Oval in London, 9-13 June 2027. The top two teams in the standings qualify.

How are World Test Championship points calculated?

A win earns 12 points, a tie 6 and a draw 4. Teams are ranked by the percentage of available points they've won, because series lengths differ.

Is there an Ashes series in 2026-27?

No. England play a one-off 150th anniversary Test against Australia at the MCG on 11-15 March 2027.

How do analysts measure home advantage in cricket?

Mostly through the home win-loss ratio and by comparing a team's batting and bowling averages at home and away.

Where can I find reliable cricket statistics?

Cricsheet offers open ball-by-ball data with attribution, ESPNcricinfo's Statsguru covers records, and the ICC and national boards publish official tables and fixtures.