Hi guys,
another 1 from todays tourney.
This is a couple of hands after the last post, so my tight image is still there (i think!). UTG in this hand has played fast when bet into in previous hands, other than that, no other reads.
Blinds 100/200 25 ante. 25 Minute levels.
effective stacks around 75bbs
I'm in CO with JJ.
UTG limps
folded to me. I raise to 500 (i missed the limp)
SB calls
BB calls
UTG calls
Flop Td 6h 5d
SB checks
BB bets 1500
UTG calls
I raise to 4900
SB folds
BB raises to 14975 and is all in
UTG folds
I fold
I'd be interested in views on the raise, if you think it's correct or not, and if correct, what the views on sizing are. I'm not concerned by UTG as based on what I had seen, if he had smashed th flop he would have raised on the flop.
My feeling is that we are a long way behind when BB shoves. I dont think he has QQ+ but i feel 555, 666 and TTT are very much a part of his range, along with big combo draws like 76dd, 87dd and some AXdd. By raise folding here are we turning JJ into a bluff? I thought I was raising for value (maybe looking for info too), but after the shove I think it's clear villain has something here that has good equity against us if nothing else.
again, thanks in advane for any comments.
Al
TPE Pro
August 25, 2012
Yeah, by raise/folding you pretty much are turning JJ into a bluff. You make it very difficult for either player in the hand to continue with anything that we beat. I don't see the BB's shoving range including too many hands we have good equity against, but then again, we have put him in a position where he can't really flat-call given the size of your raise, so his combo draws are definitely still in his range.
It's also worth noting that since he's the BB in a multiway pot and was getting great odds preflop, his range does contain combos of 65s, possibly T6s, and maybe even T5s or 65o. He's also unlikely to lead out with just a Tx hand. You're right that UTG's range is rarely a concern since he almost always has Tx or a weak flush draw, but that doesn't necessarily mean we should raise.
Think carefully about stack sizes in these spots. You put yourself in a position here of folding an overpair getting close to 2.5 to 1. That's far from ideal. I recommend plugging your estimation of his range into an equity calculator like SliceEV, and working out how much equity JJ has against it. You only need around 29% here, and I'd imagine it's quite close either way once you include the combo draws.
One other thing – don't raise for info. You don't have to wait until he's shoved all-in to work out what his all-in shoving range would be in this spot. Raising for information is an outdated concept that shouldn't really be part of your game.
November 4, 2013
Tough spot. I will offer a few non-pro thoughts.
First, you already noted that you had missed the limper. Indeed I would make it 600 or at least 560 to properly iso and try to keep out those pesky late position players you seem to be dealing with.
As played I think I think your raise on the flop is important and well timed, but I think you made it too big to fold to a shove at this point. It’s about 10k to call for like a 19k pot I think? If you don’t have reads on the BB, I think he likely has you beat but not necessarily. He could also be on a big draw or combo draw as you said, or he could simply have a strong pair of tens.
I think it is tough to fold after betting 4900 but I am curious to know what others think. I might have raised the flop lead to about 3900.
Most Users Ever Online: 2780
Currently Online:
18 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