July 15, 2013
this is one hand from WPN $1M that has been bugging me. 105 hands in, and table overall is playing fairly passive (maybe due to server maybe not…). villain in this hand (bb) has overall been fairly tight (17/10 but only at this table, 105h) but I've noted 3-4 instances of passive lines with strong hands and more aggressive lines with air, including an earlier hand against me where i fired flop/turn with AK against his TPTK and went check/check on river.
Winning Poker Network – 175/350 NL – Holdem – 8 players
Hand converted by PokerTracker 4
UTG: 14.91 BB
UTG+1: 44.35 BB
Hero (MP): 31.98 BB
MP+1: 24.24 BB
CO: 48.52 BB
BTN: 11.01 BB
SB: 61.66 BB
BB: 49.55 BB
8 players post ante of 0.1 BB, SB posts SB 0.5 BB, BB posts BB 1 BB
Pre Flop: (pot: 2.3 BB) Hero has 8 9
fold, fold, [color=red]Hero raises to 2 BB[/color], fold, fold, fold, fold, BB calls 1 BB
Flop: (5.3 BB, 2 players) T 8 4
BB checks, [color=red]Hero bets 2.65 BB[/color], BB calls 2.65 BB
Turn: (10.6 BB, 2 players) 3
[color=red]BB bets 3.59 BB[/color], Hero calls 3.59 BB
River: (17.77 BB, 2 players) 5
[color=red]BB bets 11.01 BB[/color]
in game i thought V would pretty much always call flop w AT+ and was unlikely to donk turn w/anything close to top of his range on such a dry flop, preferring to let me bet one more street. at the least, a curious card for him to lead turn. ive made up my mind that he's FOS and that i'd call and re-evaluate and the 5h doesn't change much imo. whats my play here in such a polarized spot? is a jam too impulsive/spew?
September 14, 2014
I'd fold river , although u said in OP that v tends to play aggressive with air i just think villians line does not look consistant as a bluff IMO , if anything it seems like he's got stronger hands in their range.as u know better players are very much capable of balancing their range , they may decide to c/c flop and bet turn and river with a narrow value range. as for shoving river you have to ask yourself what are you representing here? i think you would be spewing your stack for sure if u did that.
as for the turn , i must say his sizing is really weak , i'd rather call though as i don't think turning our hand into a bluff will be any good , as i dont think v is folding here enough and we arent going to get called by worse hands. So if anything i'd call turn and re-evaluate on the river, or maybe even fold turn…as nitty as that sounds.
TPE Pro
December 6, 2012
I don't get why you call this a polarized spot? If it really is polarized, then shoving makes no sense, because you can beat his bluffs by calling, and he's presumably not folding monsters. My inclination would be to call vs described Villain. Folding turn without a strong read would be ridiculous without a very good read, think about how rarely you will have a pair at all in this situation.
July 15, 2013
thanks for the replies guys. andrew you are right – polarized is definitely not the correct term since i don't expect V to take this line with his monsters, especially given prior history (which is limited for sure). basically no draws, mostly air/medium strength hands and discounting passively played overpairs whereas i can more credibly rep value.
i thought turn was pretty standard (definitely not folding and raising felt like spew). but the river decision was tricky and i only considered folding or shoving. decided against calling since i thought he had a fair amount of one pair hands with showdown value that beat me but might otherwise fold to a shove.
Most Users Ever Online: 2780
Currently Online:
25 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