// poker odds · on the flop

Odds of flopping a set

How often does a pocket pair flop a set? The short answer is below, and under it the working: the formula with the numbers put in, and the count from dealing every possible card.

set or better on the flop11.76%2,304 / 19,600
as a frequency1 in 8.51on average
odds against7.51 to 1misses to hits
by the river19.18%406,456 / 2,118,760

The working

Holding a pair, two cards of your rank are left among the 50 unseen. The flop misses only if all three cards come from the other 48:

P(no set) = C(48, 3) / C(50, 3) = 17,296 / 19,600 = 88.24%
P(set or better) = 1 − 88.24% = 11.76% = 1 in 8.51
By the turn  = 1 − C(48, 4) / C(50, 4) = 15.51%
By the river = 1 − C(48, 5) / C(50, 5) = 19.18%

The build dealt all 19,600 flops to 7♣7♦ and counted; every pair gives the same numbers because only the two matching cards matter. The engine then said what each of those flops actually makes:

What a pocket pair flops
FlopProbability1 inOdds againstCount
A set (three of a kind)10.78%9.288.28 to 12,112 / 19,600
A set and the board pairs: full house0.73%136135 to 1144 / 19,600
Both remaining cards: quads0.24%408407 to 148 / 19,600
Set or better, total11.76%8.517.51 to 12,304 / 19,600
Board trips: a full house nobody needs your pair for0.24%408407 to 148 / 19,600

Set mining: the price

Calling a raise only to flop a set wins on 11.8% of flops and gives up on the rest. To break even on the call alone, the hands where you hit must win 7.51 times the call on average, because you miss 7.51 to 1. Call 3 bb, and you need to win about 22.5 bb more when the set comes. That ignores the times a set loses (to a bigger set, a straight or a flush) and the times you hit and get no action, so the real requirement is higher. Effective stacks decide it: a call that needs 23 bb of profit cannot work with 20 bb behind.

Once you have it, see how often a set fills up, and on the pair's own page (77, say) its push/fold range at every stack depth.

More on the flop

Other odds

// how these numbers were computed
  • Counted, not quoted. tools/build-odds.mjs deals every possible flop, turn, river or starting hand and counts. Where a closed-form formula exists, the build refuses to publish unless the count matches it exactly.
  • Made hands come from the engine. Whether cards make a straight, a flush or a full house is decided by the same Rust/WebAssembly evaluator the trainer runs, not by hand-written rules.
  • Odds are not equity. Hitting your hand is not winning the pot. For that, the matchup pages deal every board against a specific hand and the spot calculator works against a range.
  • Raw data: odds.json.