Rain is the great interrupter of Australian summer cricket. Delays change the numbers in ways that are easy to forget, and the way matches are adjusted deserves a clear explanation.

How interruptions are handled

In a Test, lost time simply shortens the match, so a draw becomes more likely. In limited-overs games, the target may be revised by a method that accounts for overs and wickets in hand. The revised target is not a prediction, only an attempt at fairness.

A win after a revised target is a win, but the run rate in the scorecard is no longer a simple comparison. The side batting second had different information, which changes how it paces an innings. Look for a note about the revision before comparing two totals.

The Slotrave Australia platform is an example of how a result sheet can flag weather-affected games. That small flag is an honest piece of context.

Interruptions also change the mental side of the game. A batter returning after an hour of rain must find a rhythm again, and bowlers must reset their lines. The first overs after a break are often unusual, and a small sample of them proves little.

Rain also shapes the way a schedule is read. When a day is lost to rain, a drawn Test may say little about the relative strength of the sides. Series results should therefore be read alongside the number of overs actually bowled. Counting overs, rather than days, is the fairest way to compare matches affected by weather.

For anyone who follows betting markets, rain delays are a reminder that cricket resists tidy timetables. Agree a budget and a time limit beforehand, and be prepared to wait or to walk away.

Rain does not appear in an average, but it hides inside many of them.