View Plans & Pricing

If you are signed in and are seeing this message, please be sure you have selected a user name in My Profile. The forum requires it.
A A A
Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

Topic Rating: 0 Topic Rating: 0 Topic Rating: 0 Topic Rating: 0 Topic Rating: 0 Topic Rating: 0 (0 votes) 
sp_TopicIcon
Trying to open a bit up from BB - too much here?
wager9
Small Stakes Grinder
Members
Forum Posts: 87
Member Since:
January 5, 2015
sp_UserOfflineSmall Offline
1
July 4, 2016 - 6:18 pm
sp_Permalink sp_Print
0
LIVE WSOP Event

Blinds: 75-150-25

I have 6k. V has about 10k. V is a Euro kid about 25 yo – Italian I think and playing fairly aggressive in LP.

V opens to 450 on BTN. I call with 7T in BB – (is this too wide to call)?

POT= about 1200
Flop is T82

I check he bets 450. I call (check raise here better?)

POT= ~2100

Turn is K. I check he bets 1025. I call.

POT= about 4100

River is 4

He looks at his cards and tanks and bets 1400. Do we call?

Feel like I botched this hand on multiple levels and ways. What are your thoughts on each street?

Foucault

TPE Pro
Members
Forum Posts: 2067
Member Since:
December 6, 2012
sp_UserOfflineSmall Offline
2
July 4, 2016 - 10:41 pm
sp_Permalink sp_Print
0

Pre-flop is close, probably a call if you have a lot of confident in your post-flop play but it doesn’t sound like you do so probably folding is best. Check-raising flop is definitely not a good idea. How would you proceed if called? There are virtually no turn cards where you can bet again profitably, and even check-calling a lot of turns will be dicey.

I’d call turn and river as well. Once again, you should be thinking here in terms of range. You should be calling quite frequently given the size of Villain’s river bet, so any decent spade almost certainly belongs in your calling range.

theginger45

TPE Pro
Members
Forum Posts: 924
Member Since:
August 25, 2012
sp_UserOfflineSmall Offline
3
July 9, 2016 - 2:34 am
sp_Permalink sp_Print
0

I agree that calling down to the river is probably the way to go, but I don’t think I’d be very likely to consider defending T7o versus a 3x open. I think fold pre is better.

On the river, with villain’s sizing so small it’s likely to be fairly exploitable for you to consider folding the Ts, but since there are a ton of combos in villain’s range that include the Js/Qs/As and it seems like this river sizing is significantly less likely to be a bluff, we can consider making an exploitative fold there. So many of villain’s 2-barrelling combos are going to include one of those three cards, and I can’t see villain turning a weak showdown value hand like T9dd into a bluff too often, so we kinda need villain to be bluffing this sizing with something like QJdd or another 2-barrel bluff hand in order to be confident. We also have a ton of Js and Qs hands in our call-down range (all JsTx and QsTx combos, Qs8x, perhaps some Js9x) and some As combos (AsTx, As8x, As2x) that we can be check-raising the river with, so we don’t have to be too concerned with protecting our range.

That said, I suppose there’s a small chance villain has something like K9o with the 9s and is value-betting, so that’s one in the ‘call’ column. I doubt calling is bad but we might be able to make a big fold if we think villain’s sizing is very rarely a bluff.

Forum Timezone: America/New_York

Most Users Ever Online: 2780

Currently Online:
11 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:

Tillery999

sdmathis89

ne0x00

adrianvaida2525

Anteeater

Laggro

Forum Stats:

Groups: 4

Forums: 24

Topics: 12705

Posts: 75003

 

Member Stats:

Guest Posters: 1063

Members: 12008

Moderators: 2

Admins: 5

Administrators: RonFezBuddy, Killingbird, Tournament Poker Edge Staff, ttwist, Carlos

Moderators: sitelock, sitelock_1