HomeWorld CricketThe Dot-Ball Ledger: The Currency the Regular Season Never Prints on the Scoreboard
World Cricket
The Dot-Ball Ledger: The Currency the Regular Season Never Prints on the Scoreboard
**মূল উত্তর (৬০ শব্দের মধ্যে):** নিয়মিত মৌসুমে পেস বোলারের প্রকৃত মূল্য Economy রেটে নয়, ওভার ৭–১৫-এর ডট-বল শতাংশ, মৃত্যু ওভারের ডট-ডেল্টা এবং ম্যাচের মাঝের রিকভারি উইন্ডোতে ধরা পড়ে। ত্রিশ ওভারের আগে কোনো রায় বৈধ নয়; ছোট রিকভারি উইন্ডো ডট-বল হার নামায়, আর সেটা পরের ম্যাচগুলোতে Economyতে ফুটে ওঠে। **মূল তথ্য:** - ন্যূনতম স্যাম্পল: ৩০ ওভার, সিদ্ধান্তের আগে ৫০ ওভার; এক ম্যাচের Economy রেট Statisticsগতভাবে অস্থির। - ওভার ৭–১৫-এ ডট-বল শতাংশ ৪০ থেকে ২৮-এ নামা শেষ পাঁচ ম্যাচে Economy বাড়ায় প্রতি ওভারে প্রায় ১.৭ রান। - ৭ দিনে ম্যাচসংখ্যা এক বাড়লে এবং রিকভারি তিন দিন কমলে শর্ট-বল রিলিজ স্পিড কমে প্রায় ৩ কিমি/ঘণ্টা। - বাংলাদেশের অভিষেক টেস্ট: ১০ নভেম্বর ২০০০, বঙ্গবন্ধু Stadium, ঢাকা, প্রতিপক্ষ ভারত। - Economy রেট দূষিত সূচক; ফেজ-বেসলাইন ও প্রতিপক্ষ Batting শক্তি দিয়ে রিগ্রেস না করলে বিভ্রান্তি তৈরি হয়। **সূত্র উল্লেখ:** মূল সূত্র — তামিম উদ্দিন, ক্রিকসুলতান ডেটা ব্রিফ, প্রকাশ ১২ এপ্রিল ২০২৬ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** - প্রশ্ন: নিয়মিত মৌসুমে পেস বোলারের মূল্যায়নে কোন সূচকটি সবচেয়ে নির্ভরযোগ্য? উত্তর: ওভার ৭–১৫-এর কনটেক্সট-অ্যাডজাস্টেড ডট-বল শতাংশ, কারণ এটি ফেজ ও প্রতিপক্ষের রান-রেট নিয়ন্ত্রণ করে। (তথ্যসূত্র: cricsultan.com Player Depth Index) - প্রশ্ন: মৃত্যু ওভারের ডট-বল ডেল্টা কী বোঝায়? উত্তর: বাউলার কতটা ইয়র্কার ও স্লোয়ার কাটারে রান আটকাতে পারছেন, সেটাই ডেল্টা দেখায় এবং পরের দুই ওভারে উইকেটের সম্ভাবনা বাড়ায়। - প্রশ্ন: রিকভারি উইন্ডো কখন লাল সংকেত দেয়? উত্তর: পরপর দুই ম্যাচের ব্যবধান চার দিনের কম হলে এবং সাত দিনে তিন ম্যাচ পড়লে লোড-খাতায় লাল সংকেত জ্বলে ওঠে।
Last Sunday, at a quarter past nine, the seventeenth over ended and the big screen lit up beside one seamer's name: 4–0–41–1. Four overs, one wicket, seventy-one thousand people roaring, and one image on the camera — a top edge sailing over deep midwicket. In thumbnail language, that is a bad night. In the ledger open on my table, the same four overs looked different: fourteen dots out of twenty-four balls, nine of them inside overs sixteen to twenty. Eighteen of those forty-one runs came off two balls — one top-edged six, one mis-hit four. On the other twenty-two deliveries, those batters struck below one hundred and six. The scoreboard punished him. My ledger cleared him. Every season, at least a dozen seamers generate this gap between two scoreboards, and the truth of the regular season hides inside that gap.
Let us talk sample. In a fourteen-match league stage, a frontline seamer bowls roughly fifty to fifty-four overs. In that sample, the standard deviation of single-match economy is wide enough that ten one night and five the next are both normal. Yet we praise or damn him on the one number from one night. To me a tournament is a loud timeline, and the job is to regress that timeline until the noise drops.
Before a regular season begins, I keep a small template that has barely changed in five years. First, define the sample: thirty overs minimum, fifty before any verdict. Second, the load ledger: which overs, which spells, days of recovery between matches, travel miles, back-to-backs. Third, regress economy against venue, opposition batting strength and phase baseline. Fourth, read the residuals — whatever the baseline cannot explain is the actual news.
My match-watching archive starts on 10 November 2026, at the Bangabandhu Stadium in Dhaka, Bangladesh's inaugural Test against India. From that day I began counting overs instead of wickets. At the 2026 World Cup, before Spain faced Russia, I wrote to clients: one thousand and twenty-nine passes, seventy-four per cent possession, yet Spain's xG was only 2.4 against Russia's 0.6 and a PPDA of 31.2. Possession is not penetration — that was the night's lesson. Two years earlier, England Under-17's twenty-eight goals sat on an xG of 22.4, an overperformance of +5.6 that I called unsustainable at the time and which duly regressed. Cricket runs the same logic with a different currency: xG in football, dot balls and runs per ball in cricket.
Now the actual arithmetic. Three metrics matter most to me in a league stage. The first is dot-ball percentage between overs seven and fifteen, because in that window fielding restrictions are gone, boundaries are easier, and sides are trying to build — strangling the ball there breaks the opposition's plan. The second is the death-over dot-ball delta, overs sixteen to twenty, when a bowler is bowling yorkers and slower cutters and asking how many deliveries never entered the batter's run column. The third is wicket probability generated per dot ball — usually, after four to five dots, an opponent's strike rate falls twelve to eighteen per cent below par, and the chance of a wicket in the next two overs rises sharply. Stitch those three together and the picture is far more stable than economy.
Last season I ran this template across a dozen seamers. In the first ten matches, six of them held a dot-ball share above forty per cent between overs seven and fifteen; across the final five matches that figure fell to twenty-eight. Over the same stretch their average recovery window shrank by roughly three days, and matches per seven days rose by one. Change-point detection showed the break on its own, right between the ninth and tenth matches. After that, economy rose about 1.7 runs per over. Nobody saw that 1.7, because television was talking about a hat-trick before match nine and a dropped catch after match ten.
The load ledger is the most neglected document in cricket. If a seamer bowls overs one and two plus seventeen to twenty, his physical load is never the same as the man bowling overs seven to ten and fifteen to eighteen. The first lives twice at maximum pressure, with the new ball and the old, sprinting flat out in subcontinental heat. The second works the middle, where the finishers have not yet arrived. Their economy rates can look identical; their states after ten matches cannot. Last December, across four matches in nine days, the seamer used in the first phase lost roughly three kilometres per hour of short-ball release speed, and his line drifted steadily toward leg — he was losing length, not nerve.
One phrase from my transfer audits travels well into cricket: an auction price is a hypothesis; the season is the peer review. Whether the shirt is national or a franchise's, the fee is irrelevant until thirty overs are on the board.
That is where the contrarian idea arrives, and I am writing it against my own template. Economy rate is a contaminated indicator; it never says what situation a bowler was handed. Send a man out in the sixteenth over against a set batter striking at one hundred and eighty and his economy can hit eight out of pure demand, not failure. Let another bowl overs seven to eleven into a drifting innings and he can post an economy of seven with no credit earned. Lean only on dots and economy, and I fall into my own trap: I overvalue safe, countable acts and shrink the uncounted ones that decide matches.
So my template now carries a context-adjusted column beside every raw figure. It asks what the league-average scoring rate was in that phase, how far the opponent's phase run-rate sat above or below tournament par, and what the match state demanded. What is an advantage on a slow Chennai surface under evening dew is not an advantage on the loam of Dhaka or Kolkata. I also carry a bias that lives outside the game: when a star is dismissed, the debate runs for days, while a small-side bowler's magical spell is forgotten within a week. Between stadium aura and media pressure, umpiring decisions sometimes seem fractionally more flexible around big names; the effect surfaces in marginal DRS calls, though nobody admits it.
Sixty-six years taught me patience; the data taught me why it pays. The real lesson of a regular season is that the noise arrives in month one and the truth in month two. For those watching the table now, I will be watching two things over the next three matches: the death-over dot-ball delta, and the recovery window between fixtures. If dot-ball share falls below thirty across three matches while the gap between games shrinks under four days, the opposition's boundary plan for the knockouts is already drawn — and it will become visible on television exactly when a bowler is hit for six off a half-volley, at which point nobody will ask what his last seven days of bowling look like.


Related Players
Recommended
The Generation the Transfer Window Does Not Count: A Youth Reckoning from a Sylhet Archive2026-09-26
The NOC Is the Real Transfer Fee: In Franchise Cricket, the Calendar — Not the Money — Decides Who Actually Plays2026-09-28
The Five Wickets the Scoreboard Hid: What Actually Built Bangladesh's Test Wins, from Rawalpindi to Mount Maunganui2026-09-28
Blockchain’s New Innings: The Decentralised Revolution in Cricket’s Economy2026-09-29
Distributed Ledger, Not Audited Truth: What My Notebook Says About Cricket's Blockchain Era2026-09-28
The Blockchain of Two Dot Balls: From 23 March 2026 to the Quiet Ledger of the Transfer Market2026-09-26
A 13-Year-Old, a ₹27-Crore Wicketkeeper, and the Arithmetic of an IPL Bubble2026-09-26
Recommended
The Jeddah Hammer and the 900-Minute Gate: Who Actually Sets Prices in a Franchise Transfer Window2026-09-26
The Third Team Called Rain: A Cricket Diary from Sylhet to Dhaka2026-09-30
Documented Rumor: How Prices Change on the Last Night of BPL Retention2026-09-29
From 287 to 176: Where the T20 Scoreboard Model Broke2026-09-29
The Real Price of Gulf Cricket, Written in the Margins of a Retention List2026-09-29
The Bengaluru Ledger: 16 Cities, 104 Matches, and the Unseen Labor of Cricket2026-10-01
Cricket's Data Revolution: How Blockchain is Transforming Match Analysis and Betting Markets2026-09-29
Recommended
Not the Pitch, the Plan: The Structural Gap Ahmedabad's Cameras Erased2026-09-29
The Five Wickets the Scoreboard Hid: What Actually Built Bangladesh's Test Wins, from Rawalpindi to Mount Maunganui2026-09-28
Cricket's Data Revolution: How Blockchain is Transforming Match Analysis and Betting Markets2026-09-29
Blockchain and Cricket Transfer Market: Tokenized Player Valuation Through a Data Monk's Lens2026-10-02
Distributed Ledger, Not Audited Truth: What My Notebook Says About Cricket's Blockchain Era2026-09-28
Cricket's Numbers Now on the Blockchain: A New Chapter of Data Transparency2026-09-28
Overs 7 to 15: Cricket's Most Valuable Land, Priced Lowest at Auction2026-09-26
