होमAsian CricketSylhet's 78th Over: Hasan's Near Hat-trick, the DRS Verdict and Shadman's Ankle
Asian Cricket

Sylhet's 78th Over: Hasan's Near Hat-trick, the DRS Verdict and Shadman's Ankle

**मुख्य उत्तर (≤60 शब्द)**: सिलहट टेस्ट के दूसरे दिन वेस्टइंडीज़ ने 78 ओवर में 291/6 बनाया, जबकि हसन महमूद ने लगातार दो गेंदों पर दो विकेट लिए और तीसरी गेंद पर बिशप का एलबीडब्ल्यू फैसला डीआरएस से पलट गया, जिससे हैट्रिक नहीं मिली। उसी ओवर में सलामी बल्लेबाज़ शादमान इस्लाम का बायां टखना ज़मीन में फँसने से स्ट्रेचर पर मैदान से बाहर जाना पड़ा। **मुख्य तथ्य**: - वेस्टइंडीज़ पहली पारी में 78 ओवर पर 291/6, लगभग 3.7 रन प्रति ओवर की धीमी गति। - हसन महमूद के दो-में-दो विकेट तीन गेंदों का नमूना; हैट्रिक डीआरएस रिव्यू से रुकी। - शादमान इस्लाम का बायां टखना फील्डिंग के दौरान मिट्टी में फँसा; इलाज नाकाम होने पर स्ट्रेचर। - पहला दिन रोशनी कम होने से जल्दी खत्म हुआ, दूसरा दिन तय समय पर शुरू हुआ। - आईसीसी नियम: कंकशन के अलावा किसी चोट पर मैच के भीतर लाइक-फॉर-लाइक रिप्लेसमेंट नहीं। **स्रोत**: बांग्लादेश-वेस्टइंडीज़ सिलहट टेस्ट की लाइव मैच रिपोर्ट (मूल प्रकाशन तिथि स्रोत सामग्री में उपलब्ध नहीं; चोट का निदान भी रिपोर्ट में अपुष्ट, आगे विवरण की घोषणा)। खिलाड़ी करियर आँकड़े स्रोत में नहीं दिए गए, अतः कोई संख्या दावा नहीं किया गया। | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर**: प्र. क्या महफ़िज़ुल इस्लाम रोबिन इस टेस्ट में शादमान की जगह बल्लेबाज़ी कर सकते हैं? उ. नहीं — आईसीसी खेल शर्तों के तहत कंकशन के अलावा किसी भी चोट पर मैच के भीतर लाइक-फॉर-लाइक रिप्लेसमेंट नहीं मिलता; वे केवल सब्स्टिट्यूट फील्डर हैं। प्र. हैट्रिक क्यों नहीं मिली? उ. तीसरी गेंद पर अंपायर ने बिशप को आउट दिया, बल्लेबाज़ के रिव्यू में निर्णय पलट गया, अतः यह प्रक्रिया का परिणाम था, गेंद की चूक नहीं। प्र. सिलहट में बांग्लादेश के लिए अगला निर्णायक क्षण कौन सा है? उ. 80वें ओवर की दूसरी नई गेंद — वेस्टइंडीज़ को 330 से नीचे रोकना या 350 पार होने देना यहीं तय होगा; cricsultan.com Player Depth Index के अनुसार बांग्लादेश की शीर्ष क्रम गहराई पहले से पतली है।

The first ball of the 78th over. Mehidy Hasan Miraz, mid-spell, into his rhythm. Aamir Jangoo flicked towards the leg side, and as Shadman Islam ran and bent to cut it off, his left ankle caught in the turf and stayed there while the rest of him kept going. The physio came. Then the stretcher. In Test cricket a stretcher is a sentence, not a footnote — do not read it as an ordinary tweak.

Earlier the same morning, Hasan Mahmud had taken two wickets in two deliveries. On the third, the umpire gave Bishop out LBW; the batter reviewed; the decision was overturned. No hat-trick. But the ball did not lose that contest — the technology won it.

Sylhet's 78th Over: Hasan's Near Hat-trick, the DRS Verdict and Shadman's Ankle

Let me put one claim down at the front, plainly, because deferring it would be dishonest: the bowling control Bangladesh have built at Sylhet is currently masking the structural weakness that will surface in their own innings — the top order. That assertion can be falsified. If Shadman bats tomorrow and Bangladesh take a first-innings lead, my count was wrong. But the claim first, the caveats after.

I am filing from Manchester — off a stream, a scorecard, and an audio feed that reached me late. I do not have the heat of the ground. I have over numbers. And right now the over numbers are doing the loudest talking. I watch the same overs three times before I commit; 4,300 deliveries logged with the audio track open in the bio-secure summer of 2026 fixed that habit permanently.

Sylhet's 78th Over: Hasan's Near Hat-trick, the DRS Verdict and Shadman's Ankle

Context: what 291 for 6 actually means

Sylhet International Cricket Stadium, day two, first innings, West Indies 291 for 6. Two hundred and ninety-one in 78 overs is roughly 3.7 runs per over. In Test cricket that is a slow rate, and a slow rate is itself evidence. It points to one of three things: a dry, gripping surface, spinners holding the ball, or a deliberately defensive innings. I lean toward the first — but honestly, that inference comes from an over number and a run rate alone. I have no direct surface reading. [Confidence: low to medium]

Day one closed early for bad light; day two started on time. That small difference is large. A light stoppage is not rain — the pitch stays dry, the surface does not change, only the overs disappear. And when overs disappear, the draw floor rises. In a home Test the obligation to force a result sits heavier on the host, because a draw is the cheaper commodity for them.

Then there is the technical hinge nobody should skip: over 78. In a Test the second new ball becomes available after the 80th. Bangladesh are two overs away from the single most destructive window of an innings — pace, swing and bounce against the tail. Keeping West Indies under 330 from 291 for 6, or letting them reach 360, is the first real decision of this match.

Core: three deliveries, one ankle, one rule

Start with the contradiction sitting inside the report. It attributes Hasan's two-in-two to the "new ball" on day two. But at the 78th over the second new ball is not due. One of three things is true: the report is using "new ball" loosely for the day's opening spell; the ball was changed (a scuffed-ball replacement); or the wickets fell just after the 80th over. This is not a trivial point. If those wickets came with the second new ball, they are technically a tail-end spell, not a new-ball spark. Reporting accuracy is settled exactly here. [Confidence: low]

Now Hasan himself. Two wickets in two balls is a three-delivery sample. In 2026 I counted 1,140 deliveries of Lancashire's NatWest T20 Blast footage and wrote a twelve-part breakdown of death-over geometry — and twelve parts in, the thread stopped being a thread and became a badge. Since that lesson I have stopped carving a bowler's standing out of three balls. Hasan's spell is the genuine event of this session; that part is true. But three deliveries do not carry the authority to redefine his Test record. What they reflect is a first-innings surface, an older ball, and one set batter's error.

The DRS passage looks like the least controversial thing in the report, though the coverage will sell it as a grievance. Umpire gives it out, batter reviews, ball-tracking shows a clear miss. The system did what the system is for. Losing the hat-trick was not a failure of the delivery; it was a product of process. Framing it as a milestone snatched away is sentiment wearing the clothes of fact.

Then the ankle. Shadman Islam is a left-handed opener. For a left-hand batter the front foot — the left leg — takes the brace load in the drive, and the trigger movement settles on the same leg. So the ankle that caught in the grass is the ankle that would have to brace through cover-drives in Bangladesh's innings. The right question is not whether he can field. The right question is whether he can bat. And field treatment failing before a stretcher is called is a severity signal — lateral ligament or syndesmotic (high-ankle) damage is the classic mechanism here. That is mechanism-based inference, not a diagnosis. [Confidence: medium]

There is a rule that gets mangled constantly in coverage. Under ICC playing conditions, an injury sustained during a Test does not permit a like-for-like replacement — only concussion does. An ankle is not a concussion. So Mahfizul Islam Robin, already in the squad, cannot bat in Shadman's place in this Test; he can field as a substitute, and he is the natural pick for the next one. Bangladesh's actual route is retired hurt — an injured batter may resume later with the opposing captain's consent. If he does not bat at all, Bangladesh are effectively a ten-batter side.

And a quiet sub-plot: Mehidy was bowling the 78th over, deep into a long first-innings spell. Losing day-one overs raises the workload per available over for a frontline spinner. The injury happened in his follow-through area — that is coincidence, but the workload question is not.

Contrarian: not misfortune, surface

The easiest story is "poor Shadman, unlucky." The second easiest is "Hasan's spell turned the match." Neither catches what happened. The report itself says the ankle caught in the ground — that is a statement about surface condition, not about a fragile body. If the outfield near the boundary is soft or uneven, the same accident can repeat for either side. The host board carries a duty of care, and the ICC has venue-monitoring machinery precisely for this. It is the least-written and most useful thread in the story. [Confidence: medium]

Second inversion, from the scoreboard. 291 for 6 reads like Bangladesh on top. By wickets, they are — with the ball. But day one was truncated, day two began on time, and now a specialist opener has left the field on a stretcher. The control is bowling control; the batting ledger already has a hole in it. If West Indies pass 350, the pressure lands on the weakened top order that has not yet scored a run.

And the line that keeps proving true: the 4.4-crore file stayed closed for a month, and that was the work. In 2026 I wrote a forty-page pre-auction file arguing Jos Buttler was worth double his likely price; it was right about the player and wrong about nearly every other price in the room. Sylhet is the same shape — the market story (host dominance) and the structural story (thin top order, now thinner) are separate things. The commentary box will sell the first. I am interested in the second.

Takeaway: the column the model cannot see

I keep a column for what the model cannot see. It is always full. In this match it holds exactly one item: the scan report.

Everything else can be counted. The second new ball at over 80 can be counted. Whether Bangladesh take four wickets in the next fifteen overs can be measured. Day one's lost time and the rising draw probability is arithmetic. But Shadman's ankle is a number that does not yet exist — and it will decide whether this Test is a session's flicker or a series-long crisis.

Next time you look at the Sylhet score, count the wickets first, then look at the opening pair. Whichever arrives first will tell you whose match this is.

संबंधित खिलाड़ी