Save up to 50% during The A-Game Plan Week
×

Live 5-5 250bb deep is this ever a call against a spewtard?

Posted by

Posted by posted in Mid Stakes

Live 5-5 250bb deep is this ever a call against a spewtard?

Back story on villain:
He has been playing a decent amount at my local casino recently, he is a massive spot as he has no understanding of relative hand strength and has a tendency to spew.

Examples of the evening:

Checkraising K9xx and 987ss board vs 2 villains; one seen as tight the other has an aggressive image. SRP  $150 pot

Checkraising an aggro villain and a massive nit when the aggro bet, nit 3bet and this villain checkraises with 67 on 8910 board.  $800 pot

Checkraising 85os on 842 board vs PFR. $900 pot

Hand in question

The game has been 5-5 with 10 straddle.

I open UTG+1 to 55 after UTG limps. BTN (loose passive) Calls, Villian (spewtard) SB Calls, UTG (loose aggressive, but bad LAG) calls. I have $1300 and they have me covered.

Pot $235
Flop comes AhKsQh

SB check
UTG check
Hero??? My thinking here is I should always bet, especially with the players in the hand I know I can get value from so many worse hands.

Hero $135
BTN fold
SB Checkraise $600
UTG fold
Hero????

Pot is $970
I have about $1100 behind. Villain is looking at me nervously, he is fidgeting but I really have no reads or tells on him.

In my mind I put him on a range of KQ+:JT - How close is this? as after looking on OO, QQ has about 59% against this range so this should be a clear call. But that range could be far too loose.

Post hand my thoughts are my range>his range, even my QQ here has great EQ vs his entire range but is that range assignment too loose in people's experience? How would you proceed with this hand or alternatively how would you play preflop/postflop different? :)


Thanks guys.

Loading 8 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