Nine Sixes, an Incomplete Model, and Rawalpindi's Wait

Last month, on Test debut, Razaullah made 81 off 63 balls, including nine sixes. When the scorecard opened on my monitor, my first reaction was disbelief. Nine sixes in a Test innings sits right beside Ben Stokes's all-time record of 11. In that innings, 70 of his 81 runs came in boundaries — roughly 86 percent. Sustainable Test batting usually sources 50 to 65 percent of its runs from boundaries. I noted that day: this is not only a number, it is a signal, and a signal does not always tell the whole truth.

I trace the highlight backwards until it forgets where it began. This piece is one step in that tracing. Every number has a first touch, and every first touch has a witness.

Context: what happened, and inside which structure

At Rawalpindi, Pakistan beat Sri Lanka 2-1 in the T20I series. Afterwards, head coach Mike Hesson told reporters that Razaullah is 'raw but genuinely quick,' and that he will improve under Shaun Tait's supervision — specifically learning when to use the bouncer and when the yorker. In the same remarks, Hesson praised Sahibzada Farhan's captaincy and said he has made a 'really good start.'

Here is my methodological caution, stated plainly. You cannot build a white-ball future out of one Test innings. The format is different, the ball is different, the field setting is different, the rhythm of the match is different. Carrying one format's metric into another is the oldest trap in analysis, and this story is walking straight into it.

The Rawalpindi surface is itself a variable. Historically it is pace-friendly, with good carry. So the very environment that flatters a young quick's 'pace' is the environment that produced this innings. Home ground does not always tell the truth; sometimes it inflates the praise.

In 2026, while building Ederson's pass-origin map in Manchester, I learned a habit: keep a 'fan objection' section in every scouting report. When fans raise a question, that question becomes my model's error-check. The same question matters for Razaullah: is that nine-six innings an outlier, or the start of a pattern? Will it survive away conditions, with less carry and a quieter crowd?

Core analysis: the evidence chain

Razaullah's Test debut is genuinely rare. Eighty-one runs and four wickets in the same match is a hand-count all-round debut. But — and this is the central point — it is one match. His T20I returns are far thinner: one wicket in the opening game, he missed the second, and he was wicketless in the third. In other words, of the two matches he actually bowled in, one produced no wickets.

Almost everything needed to evaluate a young quick is missing here: multiple matches, multi-format consistency, overs bowled, economy, death-over pressure. The standard T20I economy benchmark is under 7 for excellent, around 8 for average. No such baseline exists for Razaullah yet.

Beware the 'he can bat and bowl' framing. Attaching an all-rounder label after one innings is a familiar error in cricket analysis. The all-rounder identity requires multi-format, multi-match evidence, with consistency on both sides of the ball.

Hesson's own language is careful — 'raw.' Pace, yes; polish, no. The development ask is explicit: variations, and the decision of when to bowl the bouncer or the yorker. This is a control-and-economy project, not a finished product.

On Farhan, the data is even thinner. No batting numbers are given, so no technical judgment is possible. His captaincy sample is two events — the Asian Games silver and this 2-1 series win. Hesson's most honest remark is that a T20I captain's perception depends heavily on whether his bowlers execute. That means the credit for results is partly tied to bowling execution — overrating Farhan is wrong, and over-blaming him is wrong too.

Contrarian angle: correlation is not causation

This is where my real doubt sits. Rawalpindi's pace-friendly surface inflates the visual impression of a young quick's 'pace.' At home, even the fastest bowler gets the most comfortable environment. The away test — less carry, different air, a quiet crowd — is still pending. The metric we are watching is built in home conditions; nobody knows whether it survives away.

There is a hidden question attached to Tait. Tait himself was an express bowler, known for a mix of pace and erratic line. Tasking him with teaching control is a kind of coach-skill mismatch that deserves monitoring. There is also coaching-key-person risk: if the staff changes, this trajectory can stall.

And there is the commercial dimension. A raw, express Pakistani quick — who has just produced a headline Test debut — is the classic franchise-auction asset profile. The PSL and overseas leagues do not hesitate to buy 'genuine pace,' control or no control. Commercial value can outrun sporting readiness — and that is the biggest silent risk right now.

I do not worship the dashboard; I ask who is missing from it.

I ran a fan poll — asking readers whether Razaullah should play the ODI tri-series against England on the back of Rawalpindi. The votes did not change my model; they changed my level of confidence and the shape of my question. The model did not change because of the speed; it changed because you voted.

Finally, one risk. For an express quick, the biggest threat is never the opposition — it is the schedule. A Test debut, then a T20I series, then an ODI tri-series: this compressed calendar raises injury risk for a raw young quick. His age, injury history, and the overs bowled in that Test are nowhere to be found. The three inputs most needed to measure a young quick's risk are the ones missing.

Takeaway

The real test comes in the ODI tri-series against England and Sri Lanka. A wicketless T20I evening against Sri Lanka does not automatically mean good things against England's batting line. The pace will be there, that is certain; the only question is whether the control will be. And only the next matches can answer that — not a highlight.