July 7, 2012
Thought this was a v interesting hand and worth discussion from the perspective of both players in the pot. There are a number of factors to take into consideration 1) my table image should have been v tight at this point as I was playing 14/10 on stats and had open folded to several 3bets and had 3bet folded to a 4bet jam, opponent had been at table to see most of this 2) opponent is a reg and good player and we have a small amount of history 3) I had just taken a similar flop and turn betting line with top top 3 hands previous which he would have seen.
I have posted the full hand here with result because I'd like your thoughts from both perspectives. It's also important to understand that when I jammed the rvr I genuinely thought I'd made the wheel str8 and was shocked to see the pot go the other way. What im interested in is
a) How often should this line work as a bluff i.e get opponent to lay down hands that are beating us like KT, KQ, AJ, QJ, JT, TT, 99,
– could I have sold it better on rvr with a slightly bigger turn bet say close to 2/3 pot
b) If I had actually made the wheel or flush on rvr how often should I expect to get called by the same range of hands to make this profitable as oppose to a smaller value bet?
c) Facing this line with AJ how often do you make the rvr call (for your tourney life), what hands are you putting me on?
Cake Poker No Limit Hold'em Tournament – t150.00/t300.00 Blinds – 9 players
TournamentPokerEdge.com Hand History Converter
Hero (MP1): t14686.00 48.95 BBs
jimmy rustle (MP2): t19444.00 64.81 BBs
Scruffums (CO): t6992.00 23.31 BBs
immortality1 (BTN): t9895.00 32.98 BBs
CaliOnMyMind (SB): t6474.00 21.58 BBs
YugiohPro (BB): t16427.00 54.76 BBs
Rosa Klebb (UTG): t10948.00 36.49 BBs
Chipsforme? (UTG+1): t6164.00 20.55 BBs
sharkeyshark (UTG+2): t22234.00 74.11 BBs
Pre Flop: (t450) Hero is MP1 with 3 A
3 folds, Hero raises to t666, 2 folds, immortality1 calls t666, 2 folds
Flop: (t1782) J K 5 (2 players)
Hero bets t899.00, immortality1 calls t899
Turn: (t3580) 4 (2 players)
Hero bets t1678.00, immortality1 calls t1678
River: (t6936) 3 (2 players)
Hero bets t11413.00, immortality1 calls t6652 all in
Final Pot: t20240
Hero shows 3 A
immortality1 shows A J
immortality1 wins t20450.00
(Rake: t-240)
aka Prophead340 aka Prophead2000 aka Turbulence_1
PocketFives Profile: .....urbulence/
June 5, 2012
First impression is that turn sizing is too small to make the river jam look believable. Board is wet-ish on turn, and small turn bet + river jam looks a lot like a draw, rather than a strong made hand. I think the triple barrel here, especially after picking up the nut flush draw on turn, but probably have to make turn sizing more like 2Kish.
August 6, 2012
I think the problem here is that neither the turn nor river have most likely improved our hand from Villains perspective. At a more basic level of thinking, it would be something like, if I was good on the flop, im still good on the river, except for A2, which got there.
I don't think your perceived range includes hands like A2 due to your image being so tight. Also, your shove on the river looks weak more than it does look strong IMO.
He figures, ok he either has the K or he doesn't. I think your bet sizing in the turn is good, though not for an over bet on the pot. If you were holding something like AK, and wanted to play for stacks, I think you would make it bigger OTT to set up a river shove, pretty much as trips said.
Humble opinion, I'm still a noob 😀
Most Users Ever Online: 2780
Currently Online:
55 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