Commonwealth Kabaddi Championship 2026, Day 1: What the Points Table Doesn't Say — and What Is Hidden in Bangladesh's Third Place

On the first floor of the Egora Sports Complex in Ahmedabad, where the pressure machines are installed, I looked at the score sheet again before the third raid — the kind that doesn't glow like an LED screen at a cricket stadium. This was no PKL fixture: Day 1 of the Commonwealth Kabaddi Championship 2026, thirteen men's teams, two groups, and a points table you can read in five minutes. But in those five minutes, what is shown hides more than it tells.

At the end of the day I added up all five scores. Scotland beat Australia 59-30, Kenya beat Singapore 48-28, Sri Lanka beat Malaysia 48-21, Uganda beat Malaysia 45-29, and India beat England 46-26. In the Group A table, Sri Lanka, India and Uganda sit first, second and third — all three won one match each, and their order was decided purely by score difference: +27, +20, +16. In Group B, Scotland (+29) sits above Kenya (+20). The arithmetic is fully consistent — the event's ranking rule is the standard 'wins first, score difference second' — and the factual layer of the report can be trusted.

But the real problem starts right here. In Group A, Nigeria is fourth — without having played a single match. In Group B, Bangladesh is third and Canada fourth — both without having played. This is not an error in the report; it is the mechanical consequence of the table's construction. A team that has not played has a score difference of zero, and zero sits better than the difference of teams that have lost. The meaning is clear: the Day-1 standings carry almost zero predictive value.

The most important thing the table does not say: Bangladesh's third place in Group B dramatically understates its true strength.

A necessary note for readers here. If you watch kabaddi like a children's game, understand that this is a game of seven players a side on a 13m × 10m court, in which a raider enters the opponent's half, must touch a defender and return to his own half within thirty seconds, and must maintain a continuous 'kabaddi-kabaddi' chant throughout the raid. The chant breaks, the raid dies. A defender stops the raider, that is a tackle point. All seven players ruled out, that is an 'all out' with two extra points and the entire team returns to the court. This is why scoring swings in kabaddi are so fast — 40 to 50 raids per side in a match are normal, and total scores settling between 70 and 90 are common.

Now look at Day 1's five totals on that scale: 76, 69, 89, 72, 74. All fall within the band. But Scotland-Australia's 89, the highest total of the day, signals that both teams' defensive structures were weak — conceding that many points means the defences on both sides kept raiders alive for long stretches. But there is an honest problem here: this report contains no tackle points, no raid success rate, no super raid data for any match. So no firm conclusion can be drawn from that 89. It is a directional observation, not a finding.

Lovepreet Brar. That is the name that emerged from Scotland's 59-30 win — 23 raid points, the highest individual score of the day. It is the only player statistic in the entire report. Now read it with arithmetic: 23 points is at least 39 per cent of the team's 59 total, and since a team's total also includes tackle, bonus and all-out points, his share of the raid points specifically will be well above 50 per cent. A 23-point individual haul in one match implies at least three or four super raids (raids worth 3+ points). It is an excellent individual performance — and a structural vulnerability at the same time. If an opponent neutralises this one raider, Scotland's attack can stall.

Let me be direct here: Australia was the weakest defence of the day, conceding 59. A 23-point innings against the weakest defence cannot be the basis for declaring a 'breakout star.' In PKL's analytics culture, one match falls inside the noise band — establishing a raider's true level requires at least 8 to 10 matches, or a full season. What happened here is a good day, not proven talent.

The name itself carries tactical information. 'Lovepreet Brar' is a Punjabi name, and Scotland's kabaddi ecosystem is driven by the British Punjabi diaspora. Diaspora kabaddi is culturally rooted in circle style — circular field, one-on-one attack and defence, popular in Punjab's villages. Players raised in that tradition must adapt to standard style's seven-a-side positional defence, bonus line and thirty-second chant discipline. This adaptation gap is among the least-reported stories in diaspora kabaddi — and it plausibly explains that high total (89) in Scotland-Australia: weak structured defence on both sides. Here I stop myself at an honest boundary: this is a possibility, not a confirmation, because the report mentions neither standard nor circle style anywhere.

Now the part that stings me most — India's 46-26. A twenty-point margin is solid, but by India's standards it cannot be called 'impressive.' Sri Lanka's margin was +27, larger than India's. The real question the report never answers: did India field its senior national team or a development/domestic squad? Without knowing that, drawing any conclusion from 46-26 would be dishonest. And it is no small matter that the entire report contains not one statistic for any Indian player — at an event being played in India. That editorial choice is itself a signal: this report was built from a results feed or table, not from the ground.

From here I come to the biggest story of this whole event, the one the word 'Commonwealth' itself hides.

'Commonwealth' is not a neutral descriptor — it is a structural filter. Kabaddi is not part of the Commonwealth Games; the label is one of membership, not of Commonwealth Games Federation sanction. And most importantly — this filter excludes Iran. Iran is not a Commonwealth member. Iran is the team that broke India's men's gold monopoly at the Asian Games — the undisputed second power in this sport. The world's number two team is not in this tournament, and that is no accident, it is the product of branding. This is exactly what places the event below the Asian Games or the Kabaddi World Cup tier.

The direct effect falls on competitive depth. Thirteen men's teams, thin at the top and wide at the bottom. Group A is tougher than Group B on paper — it has Sri Lanka, India and Uganda. Group B has Bangladesh, which has not yet played. And here is my sharpest inference: Group B's real strongest side is Bangladesh, and today it sits third merely because it has not played. This is not the gentle 'the table can change' caveat — it tells you that the Day-1 table has almost zero predictive value, and in Group B least of all.

A line is also owed to the African teams, because the report gave them very little space. Kenya beat Singapore 48-28, Uganda beat Malaysia 45-29 — both comfortable African wins over Asian opposition. In the standard narrative of kabaddi's 'internationalisation,' African teams are usually participants, not competitors. Two African wins on the same day is a small but real signal. But with one match apiece and no tackle data, the correct conclusion is 'worth tracking,' not 'power shift.'

Back to the arithmetic I said at the start was consistent. It is consistent, but the structure carries an asymmetry that affects outcomes — Group A has seven teams, Group B has six. In a full round-robin, Group A teams play six matches and Group B teams five. Two consequences follow. First, unequal total matches make cross-group score-difference comparison less fair. Second, the incentive to 'run up the score' is sharper in the smaller group — one big win can decide the top spot. This partly explains a lopsided scoreline like Scotland's 59-30. It is not the event's fault, it is a symptom of its format — in which the rational strategy for strong teams is to maximise margins against weak opponents rather than manage minutes.

Now the counter-intuitive angle for which I gathered this whole report.

When we read a table like this, we usually make two mistakes. First: treating it as preliminary but instructive. Second: assuming the problem is merely 'the sample is small.' The real problem is not the sample size, it is the table's architecture. A team that has not played sits above a team that has lost — not an error, but the mechanical consequence of the rule, and it gives the viewer a false picture that 'Nigeria sits solidly fourth' or 'Bangladesh is third.' The real insight is not that the table can change — the real insight is that the table is already showing you a wrong order.

A second counter-angle I keep meeting at any emerging kabaddi event: we mistake a scoreline like 59-30 for 'excitement.' It is not excitement, it is structural failure. The defences on both sides leaked so many points that the match became a one-sided contest. In a format ranked by score difference that is fine for one team, but bad for the event's credibility.

Third, and perhaps most important: I have to admit that this report lacks information that makes any technical conclusion impossible — it nowhere states how many teams qualify, nor whether standard or circle style is being played. Seen honestly, the report is close to 'a points table turned into prose': zero quotes, zero sources, zero tactical description, and empty sourcing at 35 points. All of it points one way — it was built at a desk, not on the ground, possibly semi-automatically. That does not mean the facts are wrong — the score arithmetic holds — but it means we are reading a table, not a tournament.

So what should an experienced reader watch for next? For me, the real value of this table after Day 2 will arrive in the moment Bangladesh first takes the mat and we learn whether its 'third place' is a measure of genuine strength or merely a reward for not playing. And when India plays its second match, the first question should not be how many points it scored, but who was in its team. Because at an event where the world's second-biggest force (Iran) is excluded by branding, who was on the mat matters more than the table — and who is sitting in the part of that table nobody reads.