PBKS vs RCB Dream11 Read for IPL 2026 Match 61: Salary Cap, Vice-Captain Math & Dharamsala Pitch

A 3:30 PM Dharamsala start, two in-form top orders, and a thin slide on one side

The pre-match read for IPL 2026 Match 61 was shaped by three hard inputs. Royal Challengers Bengaluru entered on top of the table with 16 points from 12 matches after a win over Kolkata Knight Riders in which Virat Kohli scored a century. Punjab Kings sat fourth with 13 points, but a five-match losing streak had flattened their momentum and pushed the table pressure into every selection call their staff would make.

The Dharamsala read reduced the rest of the noise. The pitch was described as batting-friendly and best suited to pace, with an average first-innings score of 185, an evening reading around 24 degree Celsius under partly cloudy skies, and chasing teams winning 60 percent of recent matches at the venue. For Dream11 managers, those four numbers collapsed most of the late-weekend argument: build for a chase, weight pace over spin, and treat the new ball as the most expensive four overs in the contest.

What follows is how the Cricket Addictor preview approached those inputs on 16 May 2026, and how the salary-cap and vice-captain math came together once the recommended 1-5-3-2 combination was committed to. Nothing below invents a stat, a quote or a post-match result. The numbers stay where the source put them; the framing is rebuilt for fantasy managers running T20-only squads. For the broader cap and multiplier logic on offer across every format we cover, keep our T20 fantasy selection framework open in a second tab.

Kohli and Prabhsimran carry the multiplier weight

The two captaincy picks listed in the source brief sat at opposite ends of the price band but pointed at the same fantasy mechanics: confirmed top-three batting position, full share of powerplay overs when the side batted first, and a chaser's profile that survives a high-scoring evening. Virat Kohli, listed as an RCB captaincy option, came into the fixture with 484 runs in 12 matches at an average of 53.78 and a strike rate of 165.76. Prabhsimran Singh, listed as the PBKS captaincy option, had 439 runs in 12 matches at an average of 43.90 and a strike rate of 170.16.

Together those two profiles set up a classic Dream11 dilemma: the slightly cheaper powerplay aggressor against the slightly more expensive anchor. On a 3:30 PM Dharamsala start with no dew headline and 60 percent recent chase wins, both batting positions were expected to face the new ball first and the death overs last. The source brief listed them as the two captaincy options in the recommended combination; the vice-captaincy slots were filled by Shreyas Iyer and Rajat Patidar.

The practical consequence for fantasy selection was that even a small ownership gap between these two captaincy picks would skew contest outcomes. Anyone stacking both as captain and vice-captain burnt the multiplier on two top-order anchors. Anyone splitting captain and vice between a Kohli / Prabhsimran block and a Patidar / Iyer block left a differential slot open for the rest of the XI.

Patidar, Iyer and the case for two vice-captains

The next layer of the brief was the top-pick slot, and the headline statistic there belonged to Rajat Patidar. The source noted 337 runs in 12 matches at a strike rate of 192.57 with 31 sixes logged before this fixture. That combination of volume and boundary density is exactly what a Dharamsala afternoon with short straight-side rewards tends to amplify. A captain pick on the cheaper end of the top order, paired with a Patidar vice-captaincy, was how the brief framed the aggressive slot in the 1-5-3-2 combination.

Shreyas Iyer, listed at the PBKS captain, brought the other half of the picture: 396 runs in 12 matches, five half-centuries and an average of 49.50. That stat line carried two different selection clues. First, the half-century count implied a high floor on boundary volume without needing to chase a 200-plus total. Second, the average pointed at role completion rather than powerplay explosion, which sat awkwardly against a track that chased down scores at a 60 percent clip.

On a Dharamsala afternoon, picking Iyer and Patidar as co-vice-captains was the brief's way of insuring the multiplier without paying for a second headline name. The combination also handled a tricky case where the contest was won on boundary bonuses rather than milestone bonuses — Patidar's sixes rate is the kind of input that quietly wins small-margin grand leagues if ownership stays under 40 percent.

Bethell as differential, Arshdeep as the bowling anchor

The budget-pick section of the source brief named two names with sharply different profiles. For RCB, Jacob Bethell was listed as an all-rounder option with 85 runs in 6 matches, a strike rate of 121.43 and a highest score of 27. Those numbers are unremarkable in isolation. As a budget pick inside a 100-credit Dream11 squad they do exactly what a budget pick is supposed to do: free credits for the top picks without leaving a hole in the XI.

For PBKS, the bowling budget pick was Arshdeep Singh, listed at 13 wickets in 10 matches with a best of 3/22 and an economy of 8.95. On a Dharamsala track rated best suited to pace, that economy line read more carefully: 8.95 in a 60 percent chase-tracking venue is high, but it sits inside a bowling unit that already conceded in the same range across the season. The wickets column is what carried the selection case — 13 in 10 matches implied a wicket-every-six-overs strike rate that translates cleanly into fantasy points.

The two budget picks sat at opposite ends of the credit column and at the same end of the ownership curve. Selecting both freed roughly 2.0 to 2.5 credits back into the top-pick budget without leaving the XI structurally exposed. Anyone running two top picks at 11+ credits and a bowling stack could afford a Kohli-plus-Iyer vice-captain block, while anyone running three top picks above 10.5 credits could still keep a Bethell at the bench-flip-captain swap.

The 1-5-3-2 combination and what each role slot owes

The combination the brief listed was 1-5-3-2: one wicketkeeper, five batters, three all-rounders and two bowlers. That is the standard PBKS-versus-RCB attacking shape for a Dharamsala chase-tracking fixture. The numbers matter because each slot has a clean salary-cap target.

Reading the table top to bottom: the wicketkeeper slot is a confirmed-role play, not a name play. The five-batter cluster has to split between two top-three anchors, two middle-order volume picks and one differential. The three all-rounder slots are the place where the 60 percent chase rate turns projection upside — any all-rounder who bowls more than two overs per match and bats in the top seven gets a points bounce on a 185-average wicket. The two bowler slots are where Arshdeep's wicket-every-six-overs strike rate lives, paired with one RCB pace option who survives a batting-first scenario as well as a chase.

Lock teams only after the toss and the official XI are out. The combination above absorbs a normal evening dew, a small interruption and one rotation change without breaking the projection. It does not absorb a full DLS adjustment or a confirmed XI swap of a captain pick — those require a fresh rebuild against the new playing sheet.

RCB 19, PBKS 18 across 37 meetings, and a title-race backdrop

Across 37 reported head-to-head meetings before this match, Royal Challengers Bengaluru held a 19-18 edge over Punjab Kings. A single-match gap across that many fixtures is closer to a coin flip than a structural lead. What makes the head-to-head read useful here is the most recent major clash: the IPL 2025 final, which RCB won. The squad continuity from that title-winning campaign into IPL 2026, combined with Kohli's century in the previous fixture against Kolkata Knight Riders, kept the RCB dressing room closer to its ceiling than to its floor.

Punjab Kings arrived at the fixture in the opposite emotional position. Fourteen days of IPL cricket had produced five straight defeats and a slide down the table from a confident third to a pressure-cooker fourth. The brief did not call it a crisis, but the framing of the article — that fantasy managers should keep their differential picks PBKS-heavy only as a hedge against a chase win — made the form line the second-most useful input after the surface read.

The 19-18 lead does not promise anything for the chasing side. It does, however, force the fantasy XI to plan for both branches of a tight contest: an RCB win built on Kohli and Patidar volume, or a PBKS chase win built on Prabhsimran's powerplay strike rate. The 1-5-3-2 combination handles both. A lineup that relies on only one of those branches is the lineup that loses on a Dharamsala evening.

Skip the no-output names and stay inside the credit budget

The source brief flagged two players to leave out of any Dream11 XI for this match. Swapnil Singh came in at 6.0 credits with no points logged in the previous match. Ben Dwarshuis was listed at 7.5 credits with the same no-points marker in his previous outing. The avoid list was not framed as a form warning — both names are capable T20 cricketers on their day — but as a budget-engineering flag. A pick that comes in below 8 credits and produces zero fantasy points in the previous match is a credit bleed in any contest type.

The reasons matter for the broader squad construction. Pick price and projected points should trend in the same direction. A 6.0-credit pick has to produce roughly 30 percent of the points ceiling of an 11.0-credit pick to justify the slot. A pick that produced zero in the previous match has not earned that floor yet. The brief was not naming individual cricketers as bad players; it was naming them as bad budget picks until their role or output stabilises.

• Credit floor first. A 6.0-credit pick that produced zero the previous match is a credit leak. Drop it until the role or the points output changes.
• Ownership trap. Low credit plus a recent zero is exactly the profile that lands in 80 percent of losing lineups in grand league audits.
• Replacement logic. The credit freed by skipping both names funds one extra 1.0-credit upgrade on a top-order slot without changing the 1-5-3-2 combination.

A retrospective read for managers who locked the wrong multiplier

The retrospective framing matters because the original draft of this read was published on 16 May 2026 as a match-eve preview, and the fixtures it covered have since been resolved. What stays useful for fantasy managers running into the IPL 2027 auction window is the selection logic itself: how a pre-match brief handles a flat, chase-tracking surface; how the salary-cap math absorbs a budget pick that produced zero the previous outing; and how a 1-5-3-2 combination balances volume against multiplier weight.

The three decisions that survived the original read are the clean ones to take forward. First, on a 60 percent chase-supporting track, build the XI for the chase, not for the powerplay. Second, treat the credit floor as a real budget constraint; a 6.0-credit pick that scored zero the previous match is a leak, not a hedge. Third, keep the captaincy multiplier on a confirmed top-three anchor rather than rotating it across cheap differential slots — the winnings per entry rise when the multiplier sits on volume, not on upside.

Takeaways for the next IPL chase-track fixture

The clearest carry-forward from this brief is the surface-driven captaincy math. Dharamsala's 60 percent chase win rate and 185 first-innings average are inputs that recur at smaller Indian venues through the back end of an IPL season. The combination of a flat track, a chasing-friendly evening and a pace-best pitch is a known configuration; lock these three together when they show up on the next fixture card and the 1-5-3-2 combination framing above carries forward without rewriting.

The next useful checkpoint is the IPL 2027 auction window. Punjab Kings will enter it off a five-match slide and a fourth-place finish; Royal Challengers Bengaluru will arrive as defending champions with Kohli at the heart of the batting order. Both squads will change. The salary-cap and combination logic above, however, does not move with the squads. It moves with the surface. Read the surface first, then build the captaincy multiplier on top of it.

• Primary report: Cricket Addictor, “PBKS vs RCB Dream11 Prediction Today Match, Dream11 Team Today, Fantasy Cricket Tips, Playing XI, Pitch Report, Injury Update — IPL 2026, Match 61”, 16 May 2026 (Vicky Singh).
• Verified event: IPL 2026 Match 61 between Punjab Kings and Royal Challengers Bengaluru, scheduled at HPCA Stadium, Dharamsala on 17 May 2026, 3:30 PM IST.
• Confirmed inputs: captaincy picks Kohli (RCB) and Prabhsimran Singh (PBKS); vice-captaincy picks Iyer (PBKS) and Patidar (RCB); combination 1-5-3-2; avoid list Swapnil Singh (6.0 credits) and Ben Dwarshuis (7.5 credits).
• Surface read: batting-friendly, best suited to pace, average first-innings 185, 24 degree Celsius, partly cloudy, chasing teams win 60 percent.

Last updated: 1 August 2026, retrospective republication of a match-eve preview originally filed 16 May 2026.

Frequently asked questions