Horror Session - Hand 1

[Scully]

I had a horror session last night - losing nearly 5 buy ins in around 700 hands. So I'm posting a few of the hands I'm not sure if I played OK. Hand 1, I'm in the SB and flop a set. BB 33/8, Button 23/7

Titan Poker 0.10/0.20, hand converted by the iPoker Converter at Talking-Poker

saw flop | saw showdown

Button jianny ($60.10)
SB Scully77 ($19.80)
BB selrahc ($22.1
UTG fek777 ($20.00)
UTG+1 yodaenly ($25.42)

Preflop: , 2 folds, jianny calls 0.20, Scully77 calls 0.10, selrahc checks.

Flop (0.60) 6 K Q
Scully77 bets 0.40, selrahc calls 0.40, jianny calls 0.40.

Turn (1.80) 9
Scully77 bets 1.40, selrahc calls 1.40, jianny calls 1.40.

River (6.00) J
Scully77 checks, selrahc checks, jianny bets 2.50, Scully77 calls 2.50, 1 fold

jianny shows Q T
Scully77 shows 6 6

jianny wins 11.00 with A straight, King high

[mash_tun]

This is just one of those sucky hands vs. 2 loose, passive calling stations (assuming this based on available stats you posted). I think overall, you played it fine, but there are a couple of fine-tuning thoughts:

I think you could make an argument for raising preflop, since it will allow you to take the pot down on the flop at a higher % if BTN villain folds to CB's often if he misses the flop. It also will build a bigger pot for those times that you flop a set and villain gets a piece of the board. But calling is fine.

I like the lead bet on the flop; one or both of your villains likely has a piece of the flop... TPWK, MP, flush or str8 draw...make them pay. I'd consider bumping it up to a pot-sized bet...but they'll still call it if they have something (you want them to, though, to build a big pot with your big hand).

The turn makes a str8 for some of villains' holdings; I might consider checking, but I think betting is the better move vs. these types of opponents. If a villain w. these stats has turned a str8, they usually do one of 3 things: call along (slowplaying), min-reraise, or push all-in. You are very happy with all options, since you cheaply get a chance to fill your boat with the first two actions, or you can strongly consider folding if you get pushed on.

River is a horrid card; I like the check/call of a reasonable-sized bet...I think you'll get shown 2-pair hands here enough that it's profitable.

[Taardvark]

I think you played this hand quite well. You bet when you should bet and you slowed down when scare cards that very likely hit your opponent came up. I agree with Mash that calling the river is fine.

You lost about the minimum you could with a very strong second best hand. These are the hands where you really make money. When you don't lose more than other players would you are way ahead of the game.

We don't always win our best hands and I bet if you really analyze you probably find this is somewhere in your top 5 hands played in this session if not the past several sessions.

[Scully]

Thanks for the comments guys - my thoughts were pretty much along the same lines as yours which makes me happy as it seems that my thought processes are heading in the right direction. I did wonder about the bet sizes on the flop and the turn though - I wasn't sure if they were a little small. There seems a fine line between not charging enough and letting draws get there and charging so much that draws go away!!

As for raising PF - up until very recently I've been raising any pair from any position in an unraised pot to start building a pot for when I set up. I've been experimenting lately with limping when the odds are getting close to what I need (e.g.: here I'm getting 5/1 on my money by completing - I only need to get 2 BBs in the pot post flop to make a profit on the hand) and the villain(s) seem like calling stations.

[emmapeel]

I assume it was 66. I'm sure some players will be suggesting a raise here but calling is fine.

I don't think there is much to be done here. A set is such a big hand that if you are going to lose then it should be a big sum.

I'd the BB 40 or 20? I assume it is only 20.

This looks fine to me

EP

[Scully]

EP - you're right about the limits - converter was being screwy. OP has been corrected