$12 NLHE STT: HU Flush draw + gutshot.

[Boo02]

Villian Stats (VPIP/PFR/AF): 40/24/1

Villian Stats (VPIP/PFR/AF): 40/24/1

Can i play this hand other way?
I was almost shure that he hit Ace but... Still I dont see any point to play it differently.



pokerstars, Hold'em No Limit - 25/50 - 2 players
Replay this hand on CardsChat

SB (Hero): 1,276 (26 bb)
BB: 2,724 (54 bb)

Pre-Flop: (75) Hero is SB with T♦ K♦
Hero raises to 100, BB calls 50

Flop: (200) 4♥ Q♦ A♦ (2 players)
BB checks, Hero bets 100, BB raises to 312, Hero raises to 1,176 (all-in), BB calls 864

Turn: (2,552) 8♥ (2 players, 1 all-in)

River: (2,552) 6♠ (2 players, 1 all-in)

Total pot: 2,552

Showdown:
SB (Hero) shows T♦ K♦ (high card, Ace)
(Equity - Pre-Flop: 46%, Flop: 47%, Turn: 27%, River: 0%)

BB shows A♥ 7♠ (a pair of Aces)
(Equity - Pre-Flop: 54%, Flop: 53%, Turn: 73%, River: 100%)

BB wins 2,552

 

[dallam]

That's a tense hand. If opp check and we represent the Ace with a half-pot bet or the flush-draw, seeing a check-raise here for 2.12bb-s more means flush is kinda become a chasing hand, and right now a pocket 2's beating us.

Lets suppose it has Ace, we remain with 12 outs from 46 cards. (26%)
Q and a flush draw f.e. 9, 10 or J: I'm not sure if we can see re-raise here on flop. It would be risky if you have the A, you will make a 3bet and go all-in. So no re-raise here I think.
Set is pretty much closed as a re-raise all-in would be optimal pre having 2x more stack than you.
Other kind of hands: 53s, 52s, 23s - these can be breakable too such as mentioned Q and a flush blocker, but low flush draw + gutshot may behave like this.
And I think we reached all the possibilities in this action, and Ace is the answer here as a check-raise, unless a low flush draw + gutshot now wanna make a risk here. I don't think set is possible here, so as Q + flush-draw would re-raise.
It would be pretty much an upper-level fold, but seeing why Ace is still the most possible hand that opp has, I don't think we have to push our stack in for the 12 outs - unfortunately it doesn't mean that I would do this way, probably calling off cause the small stack-pressure, but let's hope the best.