[Line Check]6-MAX, 100NL - TT on monotone board

Posted by

Posted by posted in Low Stakes

[Line Check]6-MAX, 100NL - TT on monotone board

partypoker - $1 NL FAST (6 max) - Holdem - 6 players
BB: 118.36 BB (VPIP: 23.62, PFR: 19.93, 3Bet Preflop: 9.30, Hands: 1,122)
Hero (CO): 100 BB

SB posts SB 0.5 BB, BB posts BB 1 BB
Pre Flop: (pot: 1.5 BB) Hero has Ts Th
fold, fold, Hero raises to 2.31 BB, fold, fold, BB calls 1.31 BB

Flop : (5.12 BB, 2 players) 8h 7h 4h
BB checks, Hero checks

Turn : (5.12 BB, 2 players) 6h
BB bets 2 BB, Hero calls 2 BB

River : (9.12 BB, 2 players) 9s
BB bets 8 BB, Hero calls 8 BB

Thoughts:
The main spot I'm looking to discuss is the flop. It's either a bet or a check behind. If we bet we are betting as good as our entire range which allows BB to exploit and raise a huge amount of the time. We would be in a though spot to continue with a large part of our range if we get check raised.

Let's say we cbet 3BB and get check raised to 11. Villain has to win 11/19.12 or 57.29% of the time. Which means we have to defend 42.71% of the time. I doubt we can defend that % of our CO opening range.
You might say you don't need to cbet every hand. But if we only check behind non-made hands then BB can exploit by betting turn close to always.

So in my eyes I need a cbet range and a checking range.
The cbet range would be sets, 2 pair, overpairs that have no heart, Khx, some Ahx (most), overcards, gutshots, weaker made hands that need protection such as 8x. Obviously need to play with the exact numbers for balance but this is just a rough draft.
Check back range should be overpairs with hearts, small showdown such as AX and pockets 22-77 (no set), hands we gave up, and the ones not in our cbet range. Again, would need to play around for exact numbers.

What do you guys think?

Loading 0 Comments...

Be the first to add a comment

You must upgrade your account to leave a comment.

This thread has been locked. No further comments can be added.

Runitonce.com uses cookies to give you the best experience. Learn more about our Cookie Policy