Home
(0 votes) 
June 2, 2013
Offline
Hello!
A question about ICM on this spot I just played, I still think I played it right, but maybe ICM changes things.
So, the original raiser ia an agressive guy, who was raising a lot on the semi FT, and cbetting everything, the short with 2bb was sitting out, and here is my question, do I wait till he gets ko? so do I fold pre flop, or the flop?
Pacific, $2.70 Buy-in (4,500/9,000 blinds, 1,125 ante) No Limit Hold’em Tournament, 8 Players
Poker Tools Powered By Holdem Manager – The Ultimate Poker Software Suite.
SB: 702,694 (78.1 bb)
Hero (BB): 95,178 (10.6 bb)
UTG+2: 214,602 (23.8 bb)
MP1: 382,808 (42.5 bb)
MP2: 348,062 (38.7 bb)
MP3: 124,940 (13.9 bb)
CO: 14,448 (1.6 bb)
BTN: 702,268 (78 bb)
Preflop: Hero is BB with 8
9
2 folds, MP2 raises to 18,000, 4 folds, Hero calls 9,000
Flop: (49,500) 7
5 8
(2 players)
Hero checks, MP2 bets 27,000, Hero raises to 76,053 and is all-in??
May 1, 2016
Offline
Hey Almo,
As played, I think the flop decision is relatively straight forward. I do believe it would be a mistake to defend from the BB and do much of anything else after that flop. Only a 2 and a 3 are great cards for you, as the rest fill your straights or other straights and make the board scarier, or are overcards to your pair.
I think the decision in this hand is whether to defend from the BB with a hand like that and someone sitting out so short. I think because there are still 8 players left you should probably be playing it this way. If the pay jumps were that significant, like if you were down to 3, 4, or even 5 players left, it should probably be more of a consideration, but with so many players still left I think it’s okay to play it this way.
TPE Pro
August 25, 2012
Offline
Once you defend the BB I doubt you can do much else (although there’s an argument that with your stack size and that c-bet size it might be fairly likely that villain’s c-bet range includes fewer bluffs than normal), but with a 1.6bb stack at the table I’d be surprised if it was a good idea to defend your big blind with much of a range at all since the CO is virtually certain to bust within 2-3 hands.
There’s almost no advantage to defending a hand like 98o here, and making a small amount of profit by doing so has a negligible impact on your tournament EV compared to folding and letting the shorty bust.
I might find myself making some absurdly big folds in that spot. If the shorty had like 6bb it’s different, but with 1.6bb the ICM is ridiculous.
May 22, 2016
Offline
My instinct is that the ICM considerations make it a fold out of the Big Blind, but can you tell us the payout structure? What’s the next pay jump?
I think this all plays into whether to play for the win, or to play for the money jump, but as the second shortest stack in this situation, even out of the big blind I would be playing a shove or fold strategy, wherre I am only shoving my strongest hands until the micro stack busts.
February 20, 2015
Offline
I think it’s important not to overlook that the CO is sitting out. That means 5 more hands before getting blinded out, depending on when the next level comes, rather than 2–3 hands. Other factors are whether others notice the CO is sitting out, as well as whether they even notice stack size.
Also, the difference between online and live is that the online player’s hand counts when they’re all in. Live that hand is posted and folded preflop, even if all in. So it is possible that it wins and sticks around for another lap.
Most Users Ever Online: 2780
Currently Online:
28 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
bennymacca: 2616
Foucault: 2067
folding_aces_pre_yo: 1133
praetor: 1033
theginger45: 924
P-aire 146: 832
Turbulence: 768
The Riceman: 731
duggs: 591
florianm1: 588
Newest Members:
sdmathis89
ne0x00
adrianvaida2525
Anteeater
Laggro
Philbro
Forum Stats:
Groups: 4
Forums: 24
Topics: 12705
Posts: 75003
Member Stats:
Guest Posters: 1063
Members: 12007
Moderators: 2
Admins: 5
Administrators: RonFezBuddy, Killingbird, Tournament Poker Edge Staff, ttwist, Carlos
Moderators: sitelock, sitelock_1
