Odds TrainerBlackjack Strategy
Methodology

How We Compute the Odds

By Spencer S. · Reviewed August 9, 2026

Every displayed win percentage and expected value comes from one deterministic probability engine. It does not simulate millions of hands and report a sample average. It starts with the actual remaining-shoe composition and evaluates the available actions analytically, using the documented approximations below.

Current model version: 2026.08.1 · Browser probability model · Released August 9, 2026

In one sentence

We derive a dealer-outcome distribution from the current shoe proportions (conditioned on the US peek rule), then evaluate standing, hitting, doubling, and splitting against that model. The process is deterministic—not Monte Carlo—but it is not a full card-removal recursion for every future draw.

The dealer's outcome distribution

The heart of the engine is a distribution for the dealer finishing at 17, 18, 19, 20, 21, or busting given the up-card. We compute it with memoized recursion over the dealer's hand state—total and whether it is soft. Draw weights start from the actual composition of the remaining shoe, with the unseen hole card added back, so the model responds to cards that have already left the shoe. Within that calculation, future draws use the starting proportions rather than decrementing the composition after every hypothetical card.

Crucially, the distribution is conditioned on the US peek rule: when the up-card is an ace or a ten, the dealer has already checked the hole card for blackjack, so we exclude the blackjack case and renormalize. This is why our dealer-bust numbers (a 6 busts 43.9%, an ace only ~20%) match the standard published figures for a peeked game.

Your expected value for each play

With the dealer distribution in hand, we evaluate every legal action as an expected value per dollar of your original bet:

The live panel shows the modeled value of each action. Coaching uses a fresh-shoe baseline for the selected deck count and soft-17 rule, so a depleted shoe can occasionally make the live model prefer a different play. When that happens, the interface states the distinction instead of pretending the two concepts are identical.

The default game

Unless you change the settings, the trainer uses a common US shoe game: 6 decks, dealer hits soft 17, blackjack pays 3:2, double on any two cards, double after split, split to four hands, split aces get one card, no surrender. Settings change the shoe size, dealer behavior, payout, and probability inputs. The reference chart is the standard multi-deck H17/S17 card; rule-sensitive coaching is calculated separately from a fresh-shoe baseline.

The approximations — stated plainly

Two simplifications keep the model responsive enough to run in a browser:

Validation

Validation is based on named checkpoints, not on whether an output merely looks plausible. Each comparison must use the same deck count, soft-17 rule, peek rule, payout, and action assumptions. The current model is checked against the following published results:

A checkpoint passes only when the rule assumptions match and the result agrees within the tolerance expected from the fixed-proportion and split approximations. If a result does not reconcile, send the hand, rule set, expected result, and source so it can be reproduced and corrected.

Model changelog

References and validation sources

References are used as validation targets and background. Figures labeled as ours are outputs of our model under the stated rules, not copied tables — and those outputs are published in full as free, machine-readable open datasets (CSV and JSON, CC BY 4.0) so anyone can check or reuse them.

Watch the math run live.

The trainer shows the model's current estimate on every Hit, Stand, Double, and Split button as you play.

Play free

Keep reading