Two counters are at adjacent 6-deck H17 tables. Both have a running count of +6. The first counter is in the second hand of a fresh shoe — five and three-quarter decks are still behind the cut card. The second counter is at the end of the shoe; one deck remains. Both are counting Hi-Lo correctly. Both have the same running count. If they bet by RC alone, both put out the same chips. But one of them has roughly a 0.5% edge over the house, and the other has roughly a 3% edge over the house — six times the EV per dollar wagered. The difference between them isn't the count. It's the conversion.
True count is the single concept that turns Hi-Lo (or any balanced counting system) from a card-tracking exercise into something that wins money. Running count tells you how the shoe has shifted; true count tells you how much that shift is worth per dollar bet right now. This post walks through why the conversion exists, the math, the deck-estimation skill the conversion depends on, the bet ramp that hangs off the TC, and the four most common errors that quietly drain EV from counters who think they've got the conversion locked in.
Why running count alone isn't enough
The intuition: a running count of +6 means six extra low cards have come out of the shoe. Those low cards are gone. They left 10s and Aces behind. The 10-rich remainder is what gives the player an edge.
But 'six extra 10s and Aces' is a different size of edge depending on how many cards are left. If those six extras are spread across the remaining 5 decks, that's about 1.2 extra high cards per deck — a small statistical bump. If those six extras are concentrated in the final deck, that's six extra high cards in 52 — a massive concentration.
Specifically:
- Fresh 6-deck shoe with RC +6: the shoe has 1.2 extra high cards per deck. Player edge ≈ 0.5%.
- 5 decks dealt, 1 remaining, RC +6: that 1 deck has 6 extra high cards. Player edge ≈ 3.0%.
- Same running count. Different game.
True count exists to normalize for this — to convert 'extra high cards in the shoe' into 'extra high cards per deck remaining,' which is what actually drives the player's edge on the next hand dealt.
The math
The formula:
TC = RC / decks remaining
RC is the integer you've been tracking in your head. Decks remaining is your visual estimate of how many decks are behind the cut card. Divide and round.
Worked example: RC of +9 with 3 decks remaining = TC of +3. That's the insurance threshold — at TC +3 or higher, take insurance, the highest-EV deviation in the Illustrious 18.
Another: RC of +4 with 2 decks remaining = TC of +2. That's a moderate edge, typically a 2-unit bet on a standard 1-12 spread. Same RC of +4 with 4 decks remaining = TC of +1, which doesn't even hit the bet ramp — still a 1-unit bet.
Negative counts work the same way. RC of -6 with 3 decks remaining = TC of -2. That's a 1-unit (table minimum) bet, often a Wong-out signal if penetration is shallow and the deck is unlikely to recover.
Estimating decks remaining
Decks remaining is the half of the equation that almost nobody drills. The math is trivial; the estimation is the actual skill.
Two ways to estimate, both relying on the discard tray:
- Tray-fill method. Memorize what a half-deck, a full deck, a deck and a half look like in your specific casino's discard tray. Most modern shoes use a clear plastic tray; a full deck stacks to a recognizable height. After a few shoes you can eyeball the tray to the nearest half-deck without staring.
- Hands-dealt method. A typical full-table round consumes roughly 12-15 cards (3 cards per player + dealer's exposed hand). Count rounds, multiply, and subtract from the total starting cards. Less reliable than the tray method but useful as a sanity check.
TableSharp's decksRemaining helper rounds the result to the nearest half-deck. That's the precision live play actually needs — you don't need to know whether 2.3 or 2.4 decks remain; you need to know whether you're at 'about 2 decks' or 'about 2.5 decks.' The rounding error is small and dominated by other sources of variance.
Conservative rounding direction: round decks remaining DOWN. If you estimate 2.3 decks remaining, call it 2 — which makes your TC larger (more conservative bet-sizing aggressiveness). You'd rather slightly overbet a hot shoe than slightly underbet it. Same logic for slightly small TC — you'd rather miss a deviation by being too cautious than execute a deviation that wasn't actually warranted.
The bet ramp
The TC drives the bet ramp. The classic 1-12 spread example, straight from TableSharp's betSpreadUnits function:
- TC ≤ 1: bet 1 unit
- TC = 2: bet 2 units
- TC = 3: bet 4 units
- TC = 4: bet 8 units
- TC ≥ 5: bet 12 units
Unit is your table minimum. At a $25 table, that ramp goes $25, $50, $100, $200, $300. The exact ramp shape varies by spread budget and heat tolerance — a 1-8 spread is gentler, a 1-16 is sharper. The shape always has the same character: flat at neutral or negative counts, ramped aggressively above TC +1.
Why the ramp accelerates: the player's edge per round is roughly proportional to TC - 1 (TC of +1 is roughly break-even; TC of +2 is roughly 0.5% edge; TC of +5 is roughly 2% edge). To make optimal Kelly bets at each level, the bet size has to grow with the edge. Linear bet ramps under-bet the high counts and over-bet the moderate ones; the convex ramp above tracks the edge curve more closely.
Other places TC matters
Bet sizing is the obvious use, but TC also drives the Illustrious 18 deviations:
- Insurance at TC ≥ +3 — single highest-EV deviation. Below +3 never; at +3 or above always.
- Hard 16 vs 10 — stand at TC ≥ 0, hit below 0.
- Hard 12 vs 3 — stand at TC ≥ +2, hit below.
- Hard 11 vs Ace — double at TC ≥ +1.
Each of these has a specific TC threshold (the 'index') from Schlesinger's research. Above the index, deviate from basic strategy; below, play the basic-strategy answer. The deviation EV across all 18 of these adds roughly 0.10-0.15% on top of the bet-ramp gain — not optional once you're counting seriously. See the dedicated Illustrious 18 post for the full table.
The four most common conversion errors
Four mistakes show up over and over in beginner counters. Most of them happen while the conversion is being learned but linger longer than they should:
1. Betting by RC instead of TC
The most common beginner error. Bet ramp triggers on TC, not RC. Confusing the two means over-betting fresh shoes (RC +6 in a fresh 6-deck shoe is only TC +1, not a max-bet event) and under-betting deep shoes (RC +4 with 1 deck left is TC +4, a near-max-bet event). The fix: do the division every time the count changes. With practice, the division becomes automatic — you stop seeing 'RC +6' and start seeing 'TC +1' directly.
2. Dividing by cards instead of decks
Some self-taught counters divide RC by cards remaining instead of decks remaining. The math doesn't work — RC +6 / 156 cards remaining gives 0.04, which isn't a meaningful number in any bet ramp. The formula is RC / decks, not RC / cards. The conversion was designed around deck-rich-vs-deck-poor, not card-rich-vs-card-poor.
3. Rounding the wrong direction
Some counters round TC down toward zero (more conservative). That under-bets hot shoes. The standard rounding rule is to round toward the deviation that matters: for at-or-above deviations and bet ramping, round down on decks remaining (which makes TC larger). The conservative direction in counting is always toward more aggressive bet-sizing, not less — under-betting a +EV shoe leaves more money on the table than over-betting it.
4. Updating TC only between shoes
TC updates every time RC or decks-remaining changes — which is every hand. Counters who calculate TC once a shoe and lock the bet for the rest of the shoe miss the swings within the shoe. The count can move 4+ points across a single deck dealt; the bet has to move with it.
Why TC is also the thing surveillance watches
Casinos know counters bet by TC. The 'tell' that pit bosses are trained to watch for: a player who flat-bets through 80% of a shoe, then suddenly puts out a 6x bet on a hand that looks ordinary, then drops back to minimum the next hand when the dealer turns over a 7 and 10 to reset the count. That pattern is the TC bet ramp made visible.
Counter-camouflage usually means smoothing the ramp out:
- Cap your spread (1-8 is harder to spot than 1-20)
- Adjust bets between shoes rather than mid-shoe when possible
- Vary the timing of bet changes — sometimes bet up after a loss, sometimes after a win, sometimes after a neutral hand
- Occasionally bet smaller than the ramp suggests at TC +5 (small EV cost, large heat reduction)
The cover trade-off is real. A perfectly TC-correlated bet pattern earns the most EV but draws the fastest backoff. Working counters find a spot on the curve that suits their property's heat level.
Bottom line
True count is the bridge between counting (a tracking task) and counting profitably (a money-making task). Without the conversion, RC is a number without meaning at the bet level. With the conversion, every dollar wagered is sized to the actual edge of the moment.
The drill ladder for TC: get RC accuracy locked in first (25-second deck flip with clean 0), then layer the decks-remaining estimate (eyeball discard tray to nearest half-deck), then practice the division at casino speed (RC and DR change every hand, TC has to follow). Most counters spend 4-6 weeks on RC alone before adding TC; another 2-3 weeks layering the conversion before going live.