Hobart's 138-Run Margin Came Off a Resource Table: Perry's 4-9, Short's 70 at a 77 Strike Rate, and the Three Numbers the Headlines Left Out

The moment the match stopped in Hobart, Victoria had 304 runs and Tasmania had a full 35 overs. Two hours later the board read 137, in 25.2 overs. The 138-run gap that sits between those two numbers did not come from the difference between batting and bowling. It came off a resource table.

My ledger holds two separate entries for that evening. The first is an innings that folded for 137 in 25.2 overs, a rate of 5.41 an over. The second is a rule stating that a side bowled out inside a 35-over allocation is measured against a par score of roughly 275. The headlines welded the two together and produced a comfortable phrase, and the reader was left believing he had been shown something.

In the 2026 World Cup I logged 8,400 deliveries into a private Access database — line, length, seam position, shot type. At the scoring agency off Richmond Circle one habit hardened for good: the scoreboard reports the event, the rule and the context report the reason. Put both in the same box and you have made the first error, and it is always the first error that gets made.

The ledger remembers what the crowd forgets — I open it every morning.

Context: a fifty-over match wearing two frames

Settle the format first, because two frames keep bleeding into each other in this report and the bleeding is what corrupts every reading. This is a List A fixture in the Cricket Australia One-Day Cup: fifty overs, two full innings, DLS if it rains, bonus points on the table. It is neither a T20 nor a Test. Every conclusion below stays inside the fifty-over domestic context.

The second frame is selection. The two names that carry the loudest volume in this report — Tim David and Matthew Short — are discussed mainly through a national T20 and ODI lens, while the evidence is domestic List A. That is the single largest analytical trap in the source. Where the coverage mixes the two, I flag it and separate it.

The toss entry is clean: Victoria were asked to bat, meaning Tasmania chose to field. A rain forecast was in the air, so whether that was a defensible read cannot be settled without the pitch and weather data. The source carries no pitch report. I will not therefore write that the surface seamed. I will write that the 4-40 scoreline is, before any interpretation, the largest piece of evidence available — and evidence about the outcome, not about the conditions.

Record the stake as well. The report calls it a bonus-point win, which means the value of the victory was not merely two points but extra table credit for the margin. That is where the size of the win actually matters, not in the 138 in the headline. The exact bonus-point threshold lives in the playing conditions and I do not have it verified; the ledger says ‘unconfirmed’ beside that line.

Add the third fact. Rain moved the target from 305 in 50 overs to 276 in 35. The required rate moved from 6.08 to 7.89, and by the report’s own account it touched roughly ten an over at one stage of the chase. Three numbers — 304, 276, 137 — describe three different matches on the same night.

Core: decomposing the 138

Start by taking 138 apart. Victoria made 7-304 in 50 overs. Tasmania’s par score after the rain was about 275. So the batting cleared par by roughly 29 runs — good, not extraordinary. The remaining 109 runs were saved by the bowling, which is to say Tasmania finished 138 below par.

The 138 welds two different events into one figure: a genuine bowling dominance (all out for 137) and an arithmetic convention (comparison against a par score). Keep them apart and the biggest fact of the match turns out to be 25.2 overs, not 138. A side that came to bat for fifty overs did not survive half of them.

One honest word on the DLS revision. A chase of 276 in 35 overs is not an injustice — ten wickets in hand, fewer overs, and the resource table produces exactly that. What changes is the character of the match. A chase needing 6.08 in fifty overs is a patience game in which you can be 90 for 1 after twenty overs and still be alive. A chase needing 7.89 in 35 demands aggression from the first ball. Tasmania were 4-40. They had no aggression left to spend.

The rain did not take the match away; the rain closed off the only route on which Tasmania had a workable chance — a slow, low-risk fifty-over chase. I am writing that sentence carefully, because the easiest story available is that the rain flipped the result. The result had already flipped at 4-40.

Core: Perry's spell — the biggest performance, the least assessable one

Mitchell Perry: 2-6 in five overs, 4-9 in six, economy 1.5. Six overs out of an innings of 25.2 is roughly a quarter of the bowling. It is the sharpest spell of the night.

Here I apply the discipline I apply to every player-of-the-match award: this is a phase award, not a workload award. The recognition comes from leverage — new-ball wickets at 4-40 — not from volume. The award is correct. The conclusion is still incomplete.

The source gives no season aggregate for Perry, no career List A average, no pitch information. Without those three, the honest verdict is: high-impact single performance, career significance unknown. The analyst who reads 4-9 as a season trend is the same analyst who goes quiet a month later when the same bowler returns 0-68.

The signal that projects upward is the 2-6 in the first five overs — the ability to take the new ball. The signal that projects less well is the 4-9 headline, because tail-end wickets inside an already broken chase are part of that figure. My ledger keeps two columns against Perry’s name: ‘new ball — demonstrated’, ‘repeatability on a flat surface — unconfirmed’. Until the second column is filled, the first is of limited use to any selection panel.

Core: Short's 70 off 91 — a volume innings, not a credential

Matthew Short made 70 off 91, a strike rate of about 77. Rogers made 53 off 49, and the opening stand of 92 came at better than a run a ball. The first correction is this: the partnership was quick, Short individually was not. That is the correct way to read a two-paced opening stand.

The claim that Short confirmed his white-ball credentials is only half-supported. Ninety-one balls at 77 in a total of 304 is proof of occupation, not of the boundary-dominant hitting the phrase implies in the modern ODI game. The modern ODI opener’s benchmark sits around 85 to 95; an attacking opener’s role demands 95-plus. Seventy-seven is below the role.

Short’s real problem is variance, not capability. Three consecutive ducks against Pakistan and Bangladesh, and three fifties in the seven innings before that. That is not a form curve, it is a bimodal output — zero or fifty, little in between. A player with that profile never stops generating selection argument, because both sides of the argument get fresh evidence after every innings.

He is 30. ODI batting peaks between 27 and 33, which puts him at the peak with a short runway left. This is where the patience argument stops applying — patience is invested in a player who still has cycles remaining.

And the necessary caveat: this innings in Hobart says nothing about Short against the international new ball on flat subcontinental surfaces, which is precisely where the three ducks came from. A domestic List A innings does not answer an international new-ball question.

Core: Kellaway — the report's clearest data-versus-narrative contradiction

Campbell Kellaway made 69 off 71, a strike rate near 97, in a second-wicket stand of 79. As a List A innings it is good, and his share in reaching 304 is plain.

Now open the red-ball column. Last summer in the Sheffield Shield: 506 runs at 26.78 with one century. Shield top-order par is generally treated as 35 to 40. This summer: 70 runs in four innings. For Australia A against India A: 2 runs in total. Age: 23.

The ‘future Test batter’ label is not currently supported by the underlying red-ball numbers. 506 runs at 26.78, 70 runs in four innings this summer and 2 runs for Australia A is a record arguing against imminent Test selection, however good 69 off 71 looks in a one-day match. This is the source’s clearest data-versus-narrative collision, and there is no reason to soften it.

What keeps the label alive is the 105 not out in 2026 against an attack containing Rabada, Ngidi, Jansen and Nortje. That innings is three years old and it is a genuine signal, but one innings does not cancel 70 runs in four innings and a full season at 26.78. Both sit in the ledger, and both are true at once.

At 23 the window is open — I accept that, and this is exactly where I part company with the coverage cycle’s write-him-off reflex. But an open window and an earned label are two different things.

Core: David's 13 — not an innings, a format gap

Tim David was dismissed for 13. After the rain the requirement was near ten an over, and he walked in at an entry point where risk is compulsory and risk is also fatal. The report itself says he came in on a hiding to nothing.

This innings carries essentially zero analytical value, and the report’s own framing admits it. The real datum is not the 13 — it is that this was his first List A match for Tasmania since 2026. That is not a form problem, it is a format-exposure problem.

Selection in fifty-over cricket is normally built on accumulated List A volume — innings, construction through the middle overs against spin, the rhythm of a three-hour stay. David’s pathway has run through T20 franchises, where the measure of success is a twenty-ball explosion. The two skills are different and their market prices are different.

A player’s franchise price is the price of his hitting; the demands of an ODI World Cup are different — building a long innings and reading spin through the middle. The coverage treats ‘Australia’s T20 star’ as transferable credibility across formats, which is the same cross-format conflation I flag in every selection debate.

If David’s name is raised seriously for next year’s ODI World Cup, it will be a selection-policy exception, not the product of form. An exception should be called an exception in plain language. It should not be hidden inside a data set.

Core: the bonus-point win — where the size of the victory really matters

This is recorded as a bonus-point win. In a domestic fifty-over competition that is precisely where the margin carries value — the table. Nobody is awarded points for the 138 in a headline; points come from the margin. The reader who only reads the scoreboard misses the actual stake of the tournament.

I am logging that figure as unconfirmed. The bonus-point threshold is set in the playing conditions and I do not have it verified. When verification arrives, the line updates — afterwards. That is the rule of the ledger: record what is known and what is not, then interpret.

Contrarian: three easy stories this match does not support

The first easy story is that rain decided the result. A DLS revision only becomes decisive if the chasing side is still alive when the target changes. At 4-40 Tasmania had already lost the cricket; the revised target changed the size of the defeat. The distinction looks small and it is the largest distinction in the reporting, because in one story the bowler is the protagonist and in the other it is the weather.

The second easy story is that Hobart seamed. It may well have. But the evidence is the outcome, not a pitch report. Inferring conditions from a result is the same error as building a story from a scoreboard, in its second costume. I file that claim under inference at low-to-medium confidence, not under fact.

The third easy story is that Short has staked his selection claim. That is the cross-format mix again. Staying in for 91 balls on a damp, rain-affected surface is one skill; staying in against the new ball on a flat deck in Dhaka or Colombo is another, and the three ducks were an examination of the second. To turn a good domestic innings into a selection certificate you need evidence from the same format and the same conditions.

The fourth, and in my view the most expensive, is treating Perry’s 4-9 as a season trend. Six overs, a broken chase, a match reshaped by rain. The performance is real and its impact is real; its generalisation is not.

One more thing, written against myself. This match interested me because it contains three players about whom opinions already exist — Short (variance), Kellaway (the red-ball promise), David (the T20 volume). When three pre-formed opinions arrive at one match, the danger is that we read the numbers in their favour. I reversed the order this time: numbers first, then check the opinion. Kellaway’s opinion did not survive. Short’s survived halfway. David’s question was wrong to begin with — that innings says nothing about him; his format gap does.

Three claims on the record before the next round

I am writing these down ahead of the date so that I am not later allowed to say we always suspected it.

First: if Short does not hold a strike rate above 90 across his next three List A innings, the ODI selection argument returns to exactly where it stood after the three ducks. At 30, three innings is a thin runway to convert variance into record, but it is not the end of the runway.

Second: Kellaway’s Test label will be settled in the next Sheffield Shield round, not by this 69-ball innings. If he pushes his average past 35 there after 70 runs in four innings, the argument changes; if he does not, this stays a good List A innings and the label stays where it is.

Third: watch Perry on a flat, dry surface. If the five-over new-ball spell repeats over the next few fixtures, it was skill; if it returns 0-45, it was the Hobart weather. I am accepting both outcomes in advance.

Eight thousand deliveries, and the only thing that compounded was patience — but patience only pays if you wrote down in advance what you were waiting for. For me the number from this night is not 138. It is 4-40. The 138 goes into the table. The 4-40 is where the match ended, and that is a place no resource table records.