How many IPL centuries has Virat Kohli scored now?
According to the News On AIR match report, Kohli's unbeaten 105 was his ninth IPL century, a tally described as a tournament record.
An unbeaten 105 off 60 balls from Virat Kohli delivered Royal Challengers Bengaluru a six-wicket chase in Raipur, lifted the side to the top of the IPL points table, and pushed Kohli past 14,000 T20 runs in the same innings.
· Predict11 News Desk · Source: News On AIR match report
Bengaluru finished the chase at 193 for four with five balls of the innings still unused, wrapping the game up inside 19.1 overs. The win was RCB's eighth of the season and pushed them to the top of the points table ahead of the next round of fixtures. Kohli stayed at the crease through the run chase and finished on an unbeaten 105 from 60 deliveries. The innings carried eleven fours and three sixes, a strike rate of 175, and the weight of a tournament record attached to every boundary in the second half of the chase.
Rain and a wet outfield delayed the start in Raipur. When play finally got underway, RCB won the toss and chose to field. The decision gave Kohli's side first sight of a damp surface, a chasing night under lights, and a direct read on how the KKR batting order planned to pace the middle overs.
KKR closed on 192 for four in their twenty overs after being asked to bat. Angkrish Raghuvanshi led the scoring with 71, and Rinku Singh finished unbeaten on 49 to push the total past a defensible mark in the final three overs. The RCB chase was therefore set up against a target that required controlled aggression through the powerplay and disciplined hitting in the death rather than a flat-out assault from ball one.
Kartik Tyagi returned three wickets for Kolkata, a small consolation in an innings where the batters ahead of him kept finding the boundary. The wicket count frames how Kohli's unbeaten century carries a different texture from a typical chase hundred: the early loss of partners meant he could not simply farm strike at a steady tempo. Each phase of the chase asked a different question of the innings.
Kohli's unbeaten 105 was built in three distinct phases rather than a single acceleration curve. The powerplay carried a familiar RCB pattern: find the boundary at controlled risk, take the single when offered, and let the new ball wear down. The middle overs depended on rotating strike against spinners who were content to bowl wide of the off stump, and Kohli answered by stepping across and working the ball into the leg side rather than chasing the wide line. The finishing kick arrived in the seventeenth over when he cleared the infield with a controlled lofted drive and followed it with a straight six that effectively ended the contest.
The reading of the chase, more than the headline number, is what fantasy users should pay attention to. Kohli's 105 came at a strike rate of exactly 175, and most of his sixes came against bowlers who dropped short rather than against full-toss bowling. Against a target of 193, the chase template was a measured one rather than a manic one, and that detail shapes captain and vice-captain thinking in large-field contests: a chasing side does not need a 200-plus strike rate to win, it needs boundary frequency in the right overs.
What the innings does not show is also relevant. Kohli was not dismissed because the innings was complete; he was unbeaten when the winning run was hit. For fantasy captains, the signal is that his batting position remained at number three, his role did not change, and the finishing overs were shared with the lower order. The Player of the Match award followed, capping a night where his role and his output both travelled in the same direction.
The century was Kohli's ninth in the IPL, a tally the source match report frames as a tournament record. The list of IPL hundreds is short at the top because the format and the schedule make triple-figure scores genuinely rare; reaching nine means staying at the top of the order across more than a decade, surviving the format's tactical drift, and adapting as bowling attacks changed around him.
Inside the same innings, Kohli crossed 14,000 runs in Twenty20 cricket. The source match report describes him as the first Indian and the fastest player to reach the milestone, a phrasing that matters because the global T20 run list includes several overseas batters with longer T20 careers. Crossing 14,000 first among Indians places him ahead of any domestic benchmark and inside the very top of the all-time list.
Each milestone listed above belongs to a different category. The nine IPL hundreds describe consistency at the top of the order across IPL seasons. The 14,000 T20 runs describe volume across every league Kohli has played. The Raipur innings describes a specific chase night. Reading them together produces a clearer picture of the player's career arc than any one of them alone.
The honest answer is that a single innings does not shift fantasy value the way a confirmed squad change does. What it can do is reinforce an established role and nudge captaincy thinking. Predict11 users weighing captain options know that Kohli is one of two or three batters with a long track record of converting favourable match-ups into 75-plus fantasy returns. A recent unbeaten century against an opponent who used three frontline bowlers reinforces, rather than replaces, that pattern.
For multi-entry contests, the more useful read is the strike rate. Kohli's 175 in a chase of 193 says that even when the surface slows slightly, his boundary release point sits late in the innings. Predict11 readers running differential entries can pair him with a top-order partner from the opposite end, hedge the captaincy in two of three entries, and accept that the third entry will rely on the differential rather than the anchor.
The pace bowlers on either side deserve a slower look. Kartik Tyagi's three-for did not stop a chase, but it kept the dot-ball count competitive through the middle overs, and that role typically collects fantasy points even on a losing night. Tracking his role against Bengaluru in the second half of the tournament will tell users whether he keeps the death overs or moves to powerplay. The source match report does not break down his overs, so do not lock that assumption into a transfer yet.
For readers who followed the broader Predict11 News hub, this match sits inside the same verification frame as the rest of the cricket news cycle: confirmed match data first, role interpretation second, and never the other way around. Until the IPL or the franchises publish a roster update, the right fantasy move is to watch the role, not to chase the headline.
The toss went Bengaluru's way after a rain delay and a wet outfield shortened the build-up. Bowling first in those conditions is a calculated choice: the early hours of an innings on a damp surface tend to favour seam movement, and chasing sides earn a small edge because the drying surface plays more freely in the second half of the evening. RCB's call paid off. The chase did not depend on a freak batting performance; it depended on reading the conditions correctly and executing the chase template.
Looking ahead, Raipur is unlikely to host a full quota of IPL fixtures this season, and that matters for Predict11 readers who build teams around home-and-away splits. Matches at venues with a shorter IPL history tend to produce more variable fantasy point totals than matches at venues with eight years of scoring data behind them. The right response is to lower the confidence band on returns from one-off venue games and lean on aggregate roles and recent form instead.
The single most concrete update to watch, once the next round of IPL 2026 fixtures is completed, is the official points table. The News On AIR match report states that RCB's eighth win of the season moved the team to the top of the points table. That phrasing is precise: Bengaluru is at the summit on the night of this match, not yet the champion of the league stage. The next time the IPL publishes an updated standings table, the question is whether RCB holds first place or slips behind a side that has played one match fewer. Any drop, any rise, and any net run rate movement is directly verifiable from the official IPL standings rather than from secondary commentary.
The second verifiable update is the formal IPL confirmation of Kohli's 14,000 T20 run milestone. The News On AIR report describes him as the first Indian and the fastest player to reach the mark. The IPL's own statistical database is the authoritative source for that phrasing, and the next time the league publishes a career-milestones listing, Kohli's entry should appear at the top of the Indian column. Until the league does so, the framing in this report is sourced to one news outlet and should be treated as provisional.
For readers planning fantasy teams this week, the right frame is unchanged: captain options come from confirmed role and recent form, differentials come from bowlers likely to bowl at the death, and the next concrete reason to revisit Kohli's price is the points table update rather than the next innings itself. If Bengaluru remains at the top and Kohli's next score is a 30-plus, the captaincy case does not change. If Bengaluru slips and Kohli makes a low score, the case does not collapse either. The single innings at Raipur is supporting evidence, not a season-defining signal.
According to the News On AIR match report, Kohli's unbeaten 105 was his ninth IPL century, a tally described as a tournament record.
Yes. The same match report states that Kohli became the first Indian and the fastest player overall to pass the 14,000 T20 run mark during the chase.
KKR posted 192 for four in twenty overs, and RCB chased it down with four wickets down in 19.1 overs, a margin of five balls and six wickets.
Kohli was named Player of the Match for his unbeaten 105 off 60 balls.
A single innings confirms an existing role rather than a new one. Captaincy decisions for Kohli this week should weigh the opponent match-up and recent form rather than this innings alone.
Track the next RCB fixture, captain-choice signals and tournament context through the IPL 2026 hub.