61 Raids, Two Conversion Rates: The Column Bengaluru's Win Kept Off the Scoreboard

9:47 PM, 31st minute of the second half: Bengaluru's left raider went for a dubki. The defender caught the ankle, the referee awarded two points, and the stadium noise paused for a second. I had watched that moment twice — once for the story, once muted with a stopwatch. The second viewing showed something the scoreboard never did: in the fourteen minutes before that raid, Bengaluru had attempted nine raids, five of which began with a dubki and three in which the raider changed his entry angle to pull the second defender toward him. This is not taxonomy, just a count — and that count is the real story of this match. At this stage of the season Bengaluru's position was clear: two wins, two losses in the last four, and in both losses the count of forced errors on do-or-die raids was in double digits. Since the start of the season I have kept my own log of every team's raid outcomes — entry angle, cant speed, second defender position, escape type. I built this log in 2026, when I spent four months flat on my back after knee surgery, watching the 2026 World Cup final frame by frame. Back then I thought eleven categories would make kabaddi legible. Today I know three are enough — the other eight stay in the notebook, not in the article. In this match those three were: the angle the raider entered from, when the defensive chain broke, and how the escape happened. Bengaluru attempted 61 raids. They converted 23 points — a 37.7 percent conversion rate. But there is a second column that never makes commentary: of those 61, 19 were raids where the raider made contact but got no point — forced errors. Eleven of these came on do-or-die raids. In the first half, six of those eleven fell in that bracket, and Bengaluru trailed on the scoreboard. In the second half, the same raider crossed the bonus line directly three times on do-or-die raids, without a dubki, without an ankle hold. This was not a tactical shift — it was an angle shift. I had seen this pattern once before, across nine days of tape in Jakarta 2026. In that semifinal India lost 18-27 and I charted all 27 Iranian points. The conclusion: most came from forced errors on India's do-or-die raids, not from Iran's own raid conversion. Since then I have never written Iran as a 'spoiler' in any preview. The same applies here: a large part of Bengaluru's win came from the opposition's mistakes, but nobody made those mistakes — they were manufactured. In the second half Bengaluru's defender stepped one pace forward in the chain tackle and stopped the raider near the bonus line, and that single step turns a do-or-die raid from a 'forced error' into a 'clean escape'. Let me be clear about one thing, because this is borrowed language. Just as xG overlays in football separated shot quality from goal count, 'raid success rate' in kabaddi counts points, not raid quality. PKL's analytics culture — Super 10s, High 5s, raid-success — is the real post-2026 revolution, and India's most data-literate sports coverage after cricket. But when borrowing, remember where the analogy breaks: in xG a shot model applies to every shot; in kabaddi a raid's 'model' depends on the defender's intent, which shows up on tape but not in numbers. Now the angle outside the commentary box. The story that will form after this match is that Bengaluru made a 'magnificent second-half comeback.' In my log the cause is different: in the first half Bengaluru's defenders attempted ankle holds in 9 of 14 tackles, with only 3 succeeding. In the second half they abandoned the ankle hold and switched to the chain tackle — 7 of 11 succeeded. This is not a game of tackle points, it is a game of tackle types. And this is the lesson Indian kabaddi should have learned after 2026: Iran's defensive architecture comes from wrestling — ankle holds, chain tackles, and Fazel Atrachali's tackle-points record are all products of that school. We dismissed it as a 'spoiler' when we should have called it co-favourite. The second contrarian point is about the defensive market. At the 2026 auction I logged all twelve franchises' spends by position, ignoring the rumour cycle entirely. The pattern was blunt: the biggest defensive bids went to Iranian imports while Indian corners went cheap. Today's match shows the price of that market — the team with chain-tackle experience wins the politics of do-or-die. What Bengaluru did in the second half was not bought skill, it was taught skill. And that is the gap between auction value and court value. After the match I asked a coach outside the dressing room — not on record, only for verification — who decided to change the tackle type in the second half. The answer: 'We counted how many ankle holds we missed after the first half.' That is my entire method — the interview is a place to verify what the tape already suggested, not to discover it. And remember that in this era of medical confidentiality, only the injury information that suits the club's stock price comes out. In this match a raider had his taping changed in the 11th minute — commentary called it 'cramp', my log says 'right knee, previous injury.' Fans will never know, and that is the problem. The variable for the next match is clear: was Bengaluru's chain tackle a second-half decision or a whole-match one? If the same tackle type had been used in the first half, the score would have been 35-18 instead of 30-20 — that is my log's estimate, not a guarantee. The opposition now knows that after a dubki comes a chain, not an ankle. What the raider does next time, the tape will tell. The stadium will empty; the ledger will not.