Fixture-List Forensics: The Real Culprit Behind Patna Pirates' Defeat is the Schedule, Not a Player

The whiteboard on the dressing-room wall of the Patna Pirates still shows what it has shown for the past three weeks — seven names circled in red marker, with numbers written next to them that denote hours of sleep, not raid points. At the bottom, next to one name, is '4.5'. This board isn't from match day; it's from the night the team travelled from Telangana to Jaipur — 1,400 kilometres, one airport transit, and a raid the next evening. When I photographed the board last week, the team physio said, 'Sir, this is our scouting report.' I asked where the opponent's cover movements were, and he pointed to the other side of the board — there were only columns for travel legs and rest days. That was the moment I realised this Patna Pirates season is not just another season. It is a season of the kind of defeat that the TV camera will dismiss as a 'tackling error,' but whose roots lie in the fixture list. In the four matches Patna has lost this season, their raid success rate has been below 35% in three — the league average is 42.6%. But if you only look at that number, you will make the same mistake the commentary box makes: you will blame the raider. I have learned over eight years that whenever a team suddenly 'loses rhythm,' you should look at the calendar first, and only then name a person. Patna's current slump begins on 12 January, when the team played four matches in seven days — Telangana (home), Jaipur (away), Pune (away), and then Bengaluru (away). Total travel across these four was over 3,800 kilometres, with only one day between two of the matches. League rules require every team to play two matches a week, but the home-away balance is not the same for everyone. This season Patna has played six of their first nine matches away — the most in the league. And the most interesting part: their three 'home' matches were not in Patna at all, but at the Thyagaraj Sports Complex in New Delhi, because the Patna stadium was unavailable this season. Meaning, even their 'home advantage' was a travel leg. I wrote about this last year too, when Rajasthan lost three matches in a similar week and the captain was dropped. Back then I had a notebook with travel dates from Chennai to Jaipur. That same notebook is in my bag today, and Patna's dates for this slump are on the same page. It is no coincidence that a team's defensive sync breaks down after three consecutive away matches — it's physics, not emotion. In kabaddi, defence is a collective mechanism: the distance and timing between corners, covers, and ins. When you play on three different courts in the same week, your body takes time to adjust to the mat's grip, the hall's temperature, and the distance from the crowd. Most PKL courts do not have identical mats — some have more friction, some less. Patna's players told me that the Telangana mat makes feet slip, while Jaipur's is hard. Changing three mats in three days, and expecting to win two matches in the same week — that's a supply-chain issue more than a tactics issue. Patna's defensive coach told me in a conversation that their plan this season was 'small-ball defence' — keeping corners deep and covers close to the bonus line to force the raider into deep raids. This strategy works on grounds where the mat's grip is good and the raider has little room to turn quickly. But when you play away matches continuously, you have to adjust that distance for every mat. Against Patna this season, opposition raiders used the 'deep-to-short' transition — first going deep to pull the cover, then suddenly turning towards the bonus line. This transition was most successful against teams whose corners were tired. And Patna's corners were tired in this stretch — this isn't an excuse, it's the data from their sprint times. The team physio told me that after three consecutive away matches, the corners' 10-metre sprint times showed an average drop of 0.2 seconds. In kabaddi, 0.2 seconds means you don't even reach the tackle. Another point needs to be added here, because a big narrative has been building against Patna this season: that the reason for their defeats is their 'slow raider,' and that they should bench their star raider. I checked this narrative against the raid-by-raid logs of the last four matches. Patna's main raider attempted 38 raids in these four matches, of which 15 were successful — 39.4%. This is below his season average of 44.2%, but if you look at the timestamps of those 15 successful raids, 11 came in the first half. In the second half, his success rate was only 26%. This is not a 'slow raider' — this is a tired raider. And the cause of the fatigue is not the raider's fitness, but his workload. In this stretch, he alone took 41% of the team's total raids. The league average for this share is 32%. When your main raider goes on every third raid himself, by the fourth day his muscles cannot repeat the same effort. I asked Patna's coach directly: did you rest your raider for this stretch? His answer was clear — 'We had no option, because our second raider is injured this season.' This is where I want to take you out of the cricket-style 'workload management' framework and into kabaddi's own framework. In kabaddi, substitution rules are not as flexible as cricket's. Once a player goes out, he cannot return in the same match (with some conditions). And most importantly: in kabaddi, 'rest' doesn't just mean not playing a match, but a break from travel. In the four matches Patna played in this stretch, their main raider played the full 40 minutes in three. This number says only one thing: the team had no rotation option. And when there is no rotation option, your 'star' tires, and a tired star looks 'slow.' So what does all this mean? Does it mean Patna should drop their raider? No. It means the team should complain about their fixtures, not their raider. There is another team this season that endured a similar stretch — Jaipur Pink Panthers played three away matches in seven days in December, and their defensive sync also broke. But Jaipur had two raiders who could rotate. Patna had one. This is not a talent gap, it is a roster-construction gap. And the blame for roster construction goes to the auction, where teams spent a large part of their budget on stars and not on backups. Here is a counter-intuitive point that may seem strange to my readers: Patna's real problem is not that their raider is tired. The real problem is that the team's entire system is built around one raider. When 41% of your raid workload is on one player, your defence also becomes dependent on his rhythm. When that raider slows in the second half, pressure builds on the defence, and when pressure builds on the defence, the coach changes the defensive line. In this stretch, Patna changed their defensive positioning in three matches — pulling corners in, pushing covers back. This change looked less like tactics on the field and more like panic. And defence played with panic never wins. I remember when I first sat in the Pro Kabaddi press box in Chennai in 2026, I had a spreadsheet where I calculated every team's 'rupees per raid point.' That year Tamil Thalaivas were at the bottom of the league, and one of my editors asked if the team had no 'star.' I said that having a star is less important than having the option to rest your star. No one listened to me that year. Eight years later, the same point is written on the whiteboard in Patna's dressing room — only the names have changed. So what next? Patna's next three matches are — home (New Delhi), away (Bengaluru), and then home (New Delhi). This stretch is easier than the last one, but only because it has two 'home' matches. And as I said, for Patna, 'home' also means travel. If the coach does not bring his main raider's workload down from 41% to 32% in this stretch, we will be repeating the same story next month — except by then the 'slow raider' label will have become permanent. In kabaddi, labels become permanent, but calendars keep changing. And I always look at the calendar, because the notebook never lies — whether it is Patna's or Chennai's.