HomeWorld CricketTest Hundreds From No.9 Or Below: Where The Batting-Order Column Misleads The Ledger

Test Hundreds From No.9 Or Below: Where The Batting-Order Column Misleads The Ledger

**মূল উত্তর:** টেস্ট ক্রিকেটে ৯, ১০ বা ১১ নম্বরে ব্যাট করা ব্যাটারদের সেঞ্চুরি বিরল। ৯ নম্বরে সর্বোচ্চ স্কোর ইয়ান স্মিথের ১৭৩ (অকল্যান্ড, ফেব্রুয়ারি ১৯৯০)। ১১ নম্বরে কোনো সেঞ্চুরি নেই; সর্বোচ্চ অ্যাশটন আগারের ৯৮ (ট্রেন্ট ব্রিজ, ১০ জুলাই ২০১৩)। **মূল তথ্য:** - ইয়ান স্মিথ: ১৭৩, নিউজিল্যান্ড বনাম ভারত, অকল্যান্ড, ফেব্রুয়ারি ১৯৯০ — ৯ নম্বরে সর্বোচ্চ টেস্ট স্কোর। - স্টুয়ার্ট ব্রড: ১৬৯, ইংল্যান্ড বনাম পাকিস্তান, লর্ডস, আগস্ট ২০১০ — ট্রটের সঙ্গে ৩৩২ রানের অষ্টম উইকেট জুটি। - অ্যাশটন আগার: ৯৮, অস্ট্রেলিয়া বনাম ইংল্যান্ড, ট্রেন্ট ব্রিজ, ১০ জুলাই ২০১৩ — ১১ নম্বরে সর্বোচ্চ, অভিষেক টেস্টে। - ওয়াসিম আক্রমের ২৫৭ (শেখুপুরা, অক্টোবর ১৯৯৬) ৮ নম্বরে হওয়ায় এই তালিকার বাইরে। - জেসন গিলেস্পির ২০১* (চট্টগ্রাম, এপ্রিল ২০০৬) নাইটওয়াচম্যান হিসেবে ৩ নম্বরে, তাই তালিকার বাইরে। **সূত্র:** Wisden ক্রিকেট কুইজ, “Quiz! Which batters have Test hundreds from No.9 or below?” | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: ১১ নম্বরে কি কেউ টেস্ট সেঞ্চুরি করেছেন? উত্তর: না; সর্বোচ্চ অ্যাশটন আগারের ৯৮ (১০ জুলাই ২০১৩), যা cricsultan.com Player Depth Index-এ নিচের অর্ডারের Batting গভীরতার সূচকে প্রতিফলিত হয়। প্রশ্ন: ৯ নম্বরে সর্বোচ্চ টেস্ট স্কোর কত? উত্তর: ১৭৩, ইয়ান স্মিথ, নিউজিল্যান্ড বনাম ভারত, অকল্যান্ড, ফেব্রুয়ারি ১৯৯০। প্রশ্ন: ৯ নম্বরের সেঞ্চুরি দিয়ে ব্যাটারের সামর্থ্য মাপা যায় না কেন? উত্তর: কারণ Batting পজিশন অধিনায়ক ম্যাচের Status দেখে নির্ধারণ করেন, ফলে কলামটি সামর্থ্যের নির্ভরযোগ্য সূচক নয়।

July 10, 2026. Trent Bridge. First Test of the Ashes, and Australia's No.11 is a nineteen-year-old left-hander on debut named Ashton Agar. He falls for 98, caught at deep midwicket off a pull. It remains the highest score by anyone batting at No.11 in Test cricket. One run short, and a whole column stays empty for good.

That empty box is where this story starts. "List every batter with a Test hundred from No.9 or below" — the quiz question takes one line, and five minutes. I do not find it an easy question, because the list is not symmetrical. There are hundreds at No.9. There are hundreds at No.10. There are none at No.11. The deeper the column goes, the thinner it gets. And where the sample thins out, every conclusion belongs in the doubt column.

The Laws of cricket are simple enough: eleven players a side, and all eleven have the right to bat. That is the oddity of the game. Football does not ask its goalkeeper to score, basketball does not hand the last shot to the end of the bench. Cricket sends No.9, No.10 and No.11 out there, and every so often they make a hundred.

But those hundreds are not the same species. My ledger has three kinds of entry. There is the pure tailender, whose job is bowling and whose batting is a bonus. There is the genuine all-rounder, pushed a slot or two down by team balance. And there is the specialist batter who could not go higher because of injury or illness and had to walk out at the bottom. Three different stories, filed in the same column.

In 2026, sitting in Rangpur and logging every shot of the BPL by hand, I learned one thing — the ledger doesn't lie, but the column heading can. A batting position is a name. Batting competence is the truth underneath it. Merge the two and the arithmetic breaks.

Test Hundreds From No.9 Or Below: Where The Batting-Order Column Misleads The Ledger

If you want to build the list properly, you start at the top edge. February 2026, Auckland. New Zealand against India. The wicketkeeper Ian Smith walks in at No.9 and makes 173. It is still the highest Test score by anyone batting at No.9. I did not watch that innings live — it predates me — but the entry is marked in a different colour in my hand-kept book, because it is the ceiling of the gate.

Twenty years later, August 2026, Lord's. Stuart Broad makes 169 at No.9 against Pakistan, sharing a 332-run eighth-wicket stand with Jonathan Trott. I watched that one on television, in fragments, getting up from a study desk every few minutes. What I remember is not the runs but the picture: a No.9 driving through cover while Pakistan's fielders took a step back.

Test Hundreds From No.9 Or Below: Where The Batting-Order Column Misleads The Ledger

Now look at the gaps in the column. Wasim Akram's 257 — October 2026, Sheikhupura, against Zimbabwe — is the largest Test innings ever played by a lower-order batter. He came in at No.8. So he is not on the list. Jason Gillespie's 201 not out — April 2026, Chittagong, against Bangladesh — was made at No.3, as a nightwatchman. Also outside the gate.

Stay with that for a second. The two biggest lower-order innings in Test history, 257 and 201, both sit outside the "No.9 or below" gate. The highest score inside the gate is 173. The list we are building is therefore not a list of batting ability. It is an administrative list — a record of which column a man happened to occupy. Gillespie was at No.3 that evening only because light was fading and the captain did not want a specialist exposed. One decision, one column change, and the biggest lower-order innings in Test history vanishes from the table.

Why do No.9 hundreds happen? The mechanics are mundane. The ball is old, the shine gone. The batter is set. The field is spread. The bowlers are tired. If the pitch has gone dead by day three, the No.9 has a window. Not one of those reasons is a quality of the No.9 himself. That is the trap.

Test Hundreds From No.9 Or Below: Where The Batting-Order Column Misleads The Ledger

And one thing keeps returning: a No.9 hundred is almost always co-authored. Broad's 169 exists because Trott was making 184 at the other end. Smith's 173 sat beside another long stand. A lower-order batter cannot bat long alone, because he has to be kept alive from the other end. Credit the innings to one name and the accounting is incomplete.

The other variable in my book is leverage. A hundred at 400 for 6 and a hundred at 120 for 6 both get logged as "100", and they are not the same event. I apply a rough weight: how alive was the match when he walked in, and did the innings change the result? It is not a precise method, but it is more honest than raw runs. Under-2.5 was not a hunch; it was a spreadsheet with a pulse — and so is this.

Now the part most people avoid. The link between a hundred and ability here is correlation, not causation. And correlation's biggest problem is endogeneity: the cause is generated inside the system, not outside it. Who picks the batting position? The captain. On what basis? Match state. So our independent variable is contaminated by the dependent one. In that condition, "a hundred at No.9 means the batter has improved" does not survive.

A batter makes a hundred at No.9; that does not make him a No.7. Put him at No.7 and he may average 18 across his next ten innings. I have a rule — ten matches minimum. One hundred is not a decision. There is survivorship too: a No.9 only gets a long innings when the top order has collapsed or the pitch is flat. We see the ones who got the window; the ones who never did leave no entry at all.

Distance covered and high-intensity sprints get sold as effort metrics, yet pointless running also produces pretty numbers. A lower-order hundred works the same way. The hundred does not tell you the innings mattered. The match state does.

I recalibrate because the world does, not because the model is fashionable.

So the next time a No.9 raises his bat for a hundred, ask three questions. What was the score when he walked in? Who was at the other end? And where did he bat across his next five innings? If all three answers line up, you have a trend. If not, you have a lovely evening.

And keep an eye on the No.11 gate. Agar's 98 has stood since 2026 and nobody has broken it. Some morning, someone will. A model is a confession, not a prophecy — but the ledger stays open, and the columns stay clean.