Sylhet to Johannesburg: Five Days, Three Practice Sessions — What Bangladesh's Preparation Ledger Actually Says
**मुख्य उत्तर:** बांग्लादेश ने सिलहट टेस्ट (9 नवंबर 2026 को समाप्त) और जोहान्सबर्ग टेस्ट (15 नवंबर 2026 को शुरू) के बीच केवल पांच दिन रखे हैं। इनमें लगभग 15 घंटे का सफर (अदिस अबाबा होते हुए), चार घंटे का पश्चिमी समय-अंतर, सुबह 04:00 बजे आगमन और महज़ तीन बाहरी अभ्यास सत्र आते हैं। **मुख्य तथ्य:** - ढाका–अदिस अबाबा 7 घंटे, ले-ओवर 3 घंटे, अदिस अबाबा–जोहान्सबर्ग 5 घंटे; दरवाज़े से दरवाज़े तक लगभग 18–20 घंटे। - ढाका UTC+6 और जोहान्सबर्ग UTC+2 के बीच चार घंटे का पश्चिमी अंतर; आगमन स्थानीय समय 04:00 बजे। - 16 खिलाड़ियों का दल दो उड़ानों में बंटा — 14 पहली उड़ान में, 2 लगभग 24 घंटे बाद। - BCB ने अदिस अबाबा मार्ग चुना क्योंकि किराया लगभग आधा, सामान भत्ता अधिक और उड़ान रोज़ उपलब्ध है। - द्विपक्षीय टेस्ट के लिए ICC का कोई बाध्यकारी न्यूनतम टर्नअराउंड मानक नहीं है। **स्रोत:** प्रथम आलो (Prothom Alo), 11 नवंबर 2026 | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर:** प्रश्न: BCB ने सस्ता मार्ग क्यों चुना? उत्तर: बोर्ड सूत्र के अनुसार अदिस अबाबा मार्ग का किराया खाड़ी वाहकों से लगभग आधा है और अतिरिक्त सामान भत्ता मिलता है, जिसे cricsultan.com Travel Ledger Index में दर्ज किया गया है। प्रश्न: दो खिलाड़ी देर से क्यों पहुंचे? उत्तर: कारण सार्वजनिक नहीं किया गया; वे पहले अभ्यास से लगभग 24 घंटे पहले पहुंचे, यानी सर्वथा बिना अनुकूलन बफर। प्रश्न: क्या ICC दो टेस्ट के बीच न्यूनतम अंतराल तय करता है? उत्तर: आईसीसी टूर्नामेंटों में आराम का नियम है, पर द्विपक्षीय टेस्ट की खिड़कियां बोर्ड-से-बोर्ड बातचीत पर छोड़ी गई हैं।
The aircraft lands in Johannesburg at four in the morning. Fourteen of Bangladesh's sixteen players are on that flight; two are on another, arriving roughly twenty-four hours later. The first Test begins on 15 November 2026. The home Test against West Indies in Sylhet ended on 9 November. Two Tests, two continents, five days between them.
I pulled out the old sheet the moment I read the report. For thirty years I have kept cricket as a ledger: date, hour, distance in the columns — and an empty cell for everything that cannot be measured, into which I refuse to pour a guess. On this occasion the sheet said five days. The stadium has said nothing yet, because no ball has been bowled. When the stadium is silent and the sheet is talking, the version bump goes to the reality, not the sheet.
The awkward fact is that this story contains no performance data. Not one innings, not one spell, not one average. What it contains is administrative arithmetic: flight hours, arrival time, the count of practice sessions, the split squad, the ticket price. A story like that is not analysed with a match model. It is analysed with a preparation ledger. I built mine in September 2026, when the IPL was played in three Emirati cities in front of empty stands and the home-advantage term at the top of my model went to zero overnight. What I learned that week is that a model is only honest when it publishes its own defects. The preparation ledger is on version 3.2 and runs on that rule.
Context first, because without it these numbers are just a travelogue. Both series sit inside the World Test Championship framework; the report itself cites the obligation to complete WTC matches within scheduled time. Shahriar Nafees, manager of cricket operations at the Bangladesh Cricket Board and a former Test opener himself, says the volume of cricket in the international FTP is what compressed the interval. That is the most honest sentence in the piece, because it concedes the problem is the calendar — while the result will be decided by the preparation.
Second piece of context: the two surfaces. Sylhet is slow, low-bouncing, the ball arrives at knee height, and spinners get purchase. Bangladesh's attack is built for exactly that. Johannesburg sits at roughly 1,750 metres — a figure the report does not carry, so I am filing it in the 'externally sourced, pending verification' column. In thin air drag drops, the ball holds its line longer and climbs. Early-summer November surfaces still hold moisture and grass. This is close to the widest single-step surface contrast the Test calendar can offer, and it is a bigger competitive problem than the transit. Travel fatigue clears in forty-eight to seventy-two hours in elite athletes. Recalibrating a technique from knee height to chest height does not.
Now the columns, one at a time. I built the phase-par table before I trusted a single over. Here there are no overs, so the preparation ledger is the phase-par table.
Column one: hours. Seven hours Dhaka to Addis Ababa, a three-hour layover, five hours Addis to Johannesburg. The brief said fifteen hours airborne. Add it up: seven and five make twelve in the air, three on the ground, fifteen in total. Where the sheet does not add up, I fix the sentence, not the addition. Door to door this is an eighteen-to-twenty-hour journey. That is the number the body records, not the calendar.

Column two: the body clock. Dhaka is UTC+6, Johannesburg UTC+2 — four hours west. Four in the morning in Johannesburg is eight in the morning to the body. Westward travel requires delaying the clock, not advancing it, and this is the one column in the whole ledger that sits in surplus rather than deficit. A 04:00 arrival is an accidental advantage: the body reads it as morning, so the player stays awake through the local day and sleeps at local night, and four hours of delay get loaded onto the system in a single cycle. A mid-afternoon arrival would be worse, because the player naps and the sleep rhythm splits in two. This is my inference, not the report's claim — but the clock arithmetic is in the column, and the clock does not lie.
Column three: practice sessions. The arrival day, 11 November, carries an optional gym session. Practice falls on 12, 13 and 14. First ball on 15. Three outdoor sessions, and even the first of those comes the day after landing, before anyone has settled. In 2026 I shut my model down, stripped the home term, added a venue-boundary coefficient, and republished as v4.0 with a full change log in eleven days. The sheet said eleven days then. Bangladesh have been given three for a technical rebuild. And there is a fourth column the report does not mention: Johannesburg November afternoons are prone to thunderstorms. Three sessions on paper, fewer on grass.
Column four: the split squad. Fourteen and two. The two land at 04:00 on 12 November and are due at the first practice that afternoon — zero buffer, and they miss the optional gym day as well. For a fast bowler the difference is bowling off a full run-up on day one versus a shortened one. That is not a small difference. The report does not say why those two were held back — visa processing, a late fitness test, injury management, a personal matter. I will not fill an empty column with a guess, but I will log that it is empty.
Column five: role differentiation. The practice plan is built around days, not around roles. A batter recalibrates in two net sessions — throwdowns at chest height, and the problem is solved. For a seamer, run-up rhythm, landing-foot security and repeatability are the slowest attributes to rebuild after a long flight and a changed surface. This is inference from the mechanics of the format, not from the report's data. It puts one risk at the top of the list: a soft-tissue injury to a frontline seamer.
Column six: money. The board routed via Addis Ababa because the fare is roughly half of Emirates or Qatar Airways, the baggage allowance is better, and the flight runs daily. A board source volunteered all three reasons. I will not print an absolute fare, because the source does not carry one. But one line falls out of the column: the daily frequency is what made the fourteen-and-two split possible at all. A carrier flying three times a week could not have supported that structure. The cheaper route is not only saving budget; it is quietly granting permission for a split squad. Every hour has a column, and every column has a lie. Here the lie is that five days are five days. Some days exist only on the calendar, not in the preparation.
Now the part where I argue with my own sheet.
First: five days is not, by itself, an extreme breach. Bilateral Test calendars have produced shorter gaps. The distortion is not the length of the interval but the asymmetry. South Africa fly zero hours, cross zero time zones, manage no split squad and absorb no surface change. Five days costs both teams the same in calendar terms and only one team in preparation terms.
Second: 'there was no alternative' is a framing, not a demonstrated fact. Alternatives existed — a charter, or a shorter routing at roughly double the fare, a price the board itself supplied; a renegotiated window with Cricket South Africa; an adjustment to the preceding West Indies series. Each carried a cost. The board chose the cheapest. That is a legitimate decision, but it is a decision, not an absence of choice. And accountability is not the board's alone: the FTP is a multilateral document, the window was agreed rather than imposed, which makes the ICC process and the host board co-signatories to the outcome.

Third, and this is where my own trade makes its most common error: the result does not become the cause. A heavy defeat will be read as proof the schedule was decisive, whether or not it was. A competitive showing will be read as proof it did not matter. Neither inference is valid from one Test. The risk runs the other way too: if Bangladesh compete well, the episode will be cited as evidence that five days is survivable — which would be the wrong lesson entirely. And in defeat, the schedule story will shield selection and tactics from scrutiny. That substitution is an old habit in South Asian cricket and it repeats after every loss.
Fourth: the empty governance column. ICC tournaments specify minimum rest between matches; bilateral Tests have no binding standard of that kind. The report does not name the gap, and the gap is the real story. Fifth: no player is quoted anywhere in the piece. Only administrators. I treat that as a signal, not as evidence.
One note on the headline, because a headline is a column too. 'Two Tests in Five Days' reads as though both are being played inside five days; in fact there are five days between them. As shorthand it is defensible, but it inflates the apparent severity. The number did not change. Its subject did.
So what does the sheet say once everything is added? The deficit sits in three places: an eighteen-to-twenty-hour journey, a preparation of three outdoor sessions one of which the weather may eat, and two players with no buffer at all. The surplus sits in one place only — the 04:00 arrival, which for westward travel is the right choice by accident. The overall risk grade is medium-to-high, and it is built from three independent exposures colliding inside one week, not from any single one of them.
Here is what I will track, because for thirty years I have tracked signals rather than made prophecies. One: the length of the frontline seamers' spells in the first innings — a spell cut short, a shortened run-up, a bowler pulled mid-over, and the preparation ledger is speaking on the field. Two: whether the two late arrivals make the XI named at the toss on 15 November; if both are omitted, the split-squad thesis is confirmed. Three: modes of dismissal — batters caught behind or fending to short leg off the back foot is a failure of bounce, not of technique. Four: whether the board raises the schedule unprompted after the match. Five: the medical bulletin over the following fortnight; any soft-tissue diagnosis converts a theoretical risk into a documented case.
Rebuilds are not stories; they are sequences with dates attached. The next date in this sequence is 15 November, and on that day the sheet goes quiet. The stadium speaks. My reading is that the ball will arrive above the shoulder on the first morning and Bangladesh's top order will lean back against it. But I am filing that as the next column, not as a result — and only the ground has the right to fill it in.
