Knockout Baccarat
I was browsing the web tonight, and saw one of the game publishers that I follow placed their new Knockout Baccarat game at a casino in the UK. It’s a variation on baccarat, where you post an Ante on the Player or Banker, then they deal the first player card face up. You then decide to 2x raise your Ante, or fold. The hand is then played out following standard drawing rules. If your hand wins, then your Ante is paid even-money, and your Raise bet is paid odds depending on the losing hand total.
| Losing Total | Raise Payout |
|---|---|
| 6-8 | 2:1 |
| 4-5 | 1:1 |
| 0-3 | 1:2 |
I decided to analyze the game, to see if any part of it was countable. You never know, people make vulnerable games, and you might find some double-digit exploit. Well, to cut to the chase, this new game isn’t very countable. I did find the game was kind of pointless, and that the Player bet is a lot worse than with regular baccarat.
I ran the numbers, and there’s no decision. You always 2x Raise your Ante. You just pick Banker or Player before the hand begins, and that’s it. Folding is never even a close option. The Banker bet has a 4.72% house edge, and the Player bet has a 10.98% house edge. Before you roll over in shock, you should really divide these edges by 3, since you’re always 2x raising your Ante. So, the element-of-risk is 1.57% for Banker, and 3.66% for Player.
Update: Oh, I see. Sometimes you win more than even-money, sometimes you win less. That’s different, I guess. Still, that could be done without the needless extra step of the 2x raise. The raise becomes silly once everyone realises you always make it. (Even against a player 9, you still make the 2x Banker Raise. Folding is a mistake costing at least 31% of the Ante.)
| Banker Outcome | Net | Frequency | Probability | Return | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| win vs. 8 | 5 | 55,279,842,324,480 | 0.011060 | 0.055298 | ||||||||
| win vs. 7 | 5 | 158,356,022,816,768 | 0.031681 | 0.158407 | ||||||||
| win vs. 6 | 5 | 257,091,239,776,256 | 0.051435 | 0.257174 | ||||||||
| win vs. 5 | 3 | 209,913,277,599,744 | 0.041996 | 0.125988 | ||||||||
| win vs. 4 | 3 | 248,966,126,419,968 | 0.049809 | 0.149428 | ||||||||
| win vs. 3 | 2 | 287,320,282,048,512 | 0.057482 | 0.114965 | ||||||||
| win vs. 2 | 2 | 307,130,524,108,800 | 0.061446 | 0.122892 | ||||||||
| win vs. 1 | 2 | 327,378,644,353,024 | 0.065497 | 0.130993 | ||||||||
| win vs. 0 | 2 | 440,816,606,990,336 | 0.088192 | 0.176383 | ||||||||
| lose | -3 | 2,230,518,282,592,260 | 0.446247 | -1.338740 | ||||||||
| push | 0 | 475,627,426,473,216 | 0.095156 | 0.000000 | ||||||||
| total | 4,998,398,275,503,360 | 1.000000 | -0.047213 | |||||||||
| Player Outcome | Net | Frequency | Probability | Return | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| win vs. 8 | 5 | 55,165,968,408,576 | 0.011037 | 0.055184 | ||||||||
| win vs. 7 | 5 | 155,954,129,788,928 | 0.031201 | 0.156004 | ||||||||
| win vs. 6 | 5 | 239,782,224,326,656 | 0.047972 | 0.239859 | ||||||||
| win vs. 5 | 3 | 246,959,201,783,808 | 0.049408 | 0.148223 | ||||||||
| win vs. 4 | 3 | 267,343,809,949,696 | 0.053486 | 0.160458 | ||||||||
| win vs. 3 | 2 | 268,582,958,172,160 | 0.053734 | 0.107468 | ||||||||
| win vs. 2 | 2 | 280,469,279,004,672 | 0.056112 | 0.112224 | ||||||||
| win vs. 1 | 2 | 301,505,544,974,336 | 0.060320 | 0.120641 | ||||||||
| win vs. 0 | 2 | 414,755,166,183,424 | 0.082978 | 0.165955 | ||||||||
| lose | -3 | 2,292,252,566,437,890 | 0.458597 | -1.375792 | ||||||||
| push | 0 | 475,627,426,473,216 | 0.095156 | 0.000000 | ||||||||
| total | 4,998,398,275,503,360 | 1.000000 | -0.109777 | |||||||||
| Sidebet | Payout | Return | Ideal Countability |
|---|---|---|---|
| Player Natural Winner | 4:1 | -0.187055 | ~1.6% bet/shoe |
| Banker Natural Winner | 4:1 | -0.187055 | |
| Winner w/ 1,2,3,4 | 7:1 | -0.162387 | ~30% bet/shoe |
| Winner w/ 5,6 | 3.5:1 | -0.170433 | ~8% bet/shoe |
| Winner w/ 7 | 4.5:1 | -0.128165 | ~16% bet/shoe |
| Winner w/ 8 | 3:1 | -0.131132 | ~16% bet/shoe |
| Winner w/ 9 | 2.5:1 | -0.159784 | ~7% bet/shoe |
Two-Person Panda-8 Co-Count
There are times when you’re at a casino with a friend, and you want to count the EZ-Baccarat Dragon-7. Normally, it’s kind of boring, and you certainly don’t need two people to do it. While it’s a good advantage play, it’d be better and a lot more fun if your friend could help with the Panda-8. I’ve posted a very complicated Panda-8 count that yields about 22% of a fixed bet per shoe. I’ve also posted a super-simple Panda-8 co-count that only yields about 9% of a fixed bet per shoe, but is meant as a single-person add-on to the Dragon-7 count.
In this post, I’ve worked out a better Panda-8 co-count that can be easily tracked by a second person. You add its running count to the Dragon-7 RC to determine when to bet the Panda. The idea exploits the common values between the two counts, resulting in a simple Panda-8 co-count. I worked this out, because I plan to use it.
Here’s the taps for the Panda-8 co-count. You add its running count to the unbalanced Dragon-7 running count, and bet when the total count is +35 or higher. You’ll get about +13.4% of a fixed bet per shoe, on an average of 3.6 bets per shoe.
| Rank | Count |
|---|---|
| Six, Seven, King, Queen | +1 |
| Trey | -1 |
| Eight | -3 |
| Rank | Count |
|---|---|
| Four, Five, Six, Seven | -1 |
| Eight, Nine | +2 |
| Ace | +1 |
Panda-8 Co-Count with Dragon-7
With the simplified unbalanced count for the EZ-Baccarat Dragon-7, it’s occasionally fun to count a shoe and find opportunities to bet $25 – $100, to try to win $1000 – $4000. But overall, counting the Dragon gets pretty boring. It only takes a second to see the value of the hand, and to update your count. Then you spend a lot of time watching everyone think deeply about their next bets. Hopefully, the count gets to +32, so you can finally make a bet.
Counting the Dragon-7 would be pretty good if you could make about twice the +EV it offers (+52% of a fixed bet per shoe). Or at least it’d be fun if you could easily track the Panda-8 as well, to add some variety to the game. (I’ve previously posted a complicated Panda-8 count and a RCmin table that yields +22% of a fixed bet per shoe.)
Well, I can’t double the EV of the Dragon-7, nor can I easily get you the full +22% of the Panda. But, here’s an ultra-simplified Panda-8 co-count that you should be able to track alongside the Dragon-7. It’s an unbalanced count, for simplicity. It only has a few taps. The few (4) taps it has are equal to those of the Dragon-7 unbalanced count. Also, these are key taps (you focus on the +2 Nines for the Dragon; it uses the same +1 unbalanced Aces; finally, the -1 Fours and Fives are easy to remember, because they add up to 9). You should be able to track your main Dragon-7 count, then quickly scan the hand for its Panda-8 value.
| Card | Count Value |
|---|---|
| Ace | +1 |
| Four, Five | -1 |
| Nine | +2 |
Starting from a running count (RC) of 0, you should bet the Panda-8 when its count gets to +35. You’ll get an average of about 2 bets per shoe (when 16 cards are placed behind the cut card), and a profit of around +9.0% of a fixed bet per shoe. It’s not a whole lot, but it’ll make sitting around the baccarat table a little more fun/tolerable. Also, it’ll give you more cred with the degenerates watching their Player lines, Panda lines, and their second bankers
Thanks to Linus B for his initial work on the Panda co-count. I greatly simplified it here for us script-kiddies.
Unbalanced Dragon 7 Count
If you’re ever at an EZ-Baccarat table wondering how to properly count the Dragon-7, here’s an easy-to-use unbalanced count that you won’t forget. Unbalanced counts are very handy, because their running counts (RC) approximate true counts, without any division. They’re a nice little trick that everyone should use. I modified the count from my Dragon-7 tracking sheet post into the unbalanced count below.
You simply start the count at -32 for a new shoe, then update the running count for each card dealt, including the exposed burn card. When the running count is > 0, bet the Dragon-7 side bet. This count scheme simulates at a profit rate of +52% of a fixed bet per 8-deck shoe, when 16 cards are placed behind the cut card. You’ll get about 6.8 betting opportunities per shoe.
| Card Rank | Count Value |
|---|---|
| Ten/Face | 0 |
| Ace | +1 |
| Deuce | 0 |
| Trey | 0 |
| Four | -1 |
| Five | -1 |
| Six | -1 |
| Seven | -1 |
| Eight | +2 |
| Nine | +2 |
The variance of the bet is very high, and unless you’re heads-up with the dealer, the hand rate is very slow. If you’re wondering if you can grind out a profit from the bet, look at the outcome distribution below for a 500 unit bankroll with a +1000 unit goal, else playing for 500 shoes. While the risk of ruin is only 3.5%, you still have a 24% chance of losing after 500 shoes. Your average win is +250 units. So, if you have a $50k bankroll, can find a heads-up EZ-Baccarat table with a $100 max Dragon-7 bet, are committed to playing for hundreds of hours, and don’t draw any suspicion from casino personnel, then you can win from $50 to $100 per hour, depending on how fast you play. It might be fun for the first hour or two, but only if you hit a dragon. Try playing my Dragon-7 shoe simulator before you head out to the casino.

Easy Six Baccarat
A reader just asked about a no-commission game called Easy Six Baccarat. I’ll keep this post short, for those in-the-know. Use the simple taps (6 => -7, 7 => +3, 8 => +2, 9 => +2) and a true count threshold of 5.0. For an 8-deck shoe with 52 cards behind the cut card, you’ll net +49% of a fixed bet per shoe, on an average of 12 bets/shoe. For an 8-deck shoe with 16 cards behind the cut card, you’ll net +84% of a fixed bet per shoe, on an average of 15 bets/shoe.
For simplicity, you can use the RCmin thresholds in following table:
| hand # | Min RC Threshold | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| burn | ||||||||||||
| 1 | 40 | 40 | 39 | 39 | 38 | 38 | 37 | 37 | 36 | 36 | 35 | 35 |
| 13 | 34 | 34 | 33 | 33 | 32 | 32 | 31 | 31 | 31 | 30 | 30 | 29 |
| 25 | 29 | 28 | 28 | 27 | 27 | 26 | 26 | 25 | 25 | 24 | 24 | 23 |
| 37 | 23 | 22 | 22 | 21 | 21 | 21 | 20 | 20 | 19 | 19 | 18 | 18 |
| 49 | 17 | 17 | 16 | 16 | 15 | 15 | 14 | 14 | 13 | 13 | 12 | 12 |
| 61 | 11 | 11 | 11 | 10 | 10 | 9 | 9 | 8 | 8 | 7 | 7 | 6 |
| 73 | 6 | 5 | 5 | 4 | 4 | 3 | 3 | 2 | 2 | 2 | 1 | 1 |
Lucky 9 @ Harrah’s Rincon
There’s a new game Lucky 9 at my nearby Harrah’s Rincon that’s a hybrid between baccarat and blackjack. It plays like simplified blackjack, where you can only hit once, and hand totals are between 0-9. Like blackjack, you start with two cards, and the dealer exposes their top card. Like baccarat, hand values are equal to the last digit of the sum of the cards. The best hand is a Lucky 9, which is a two card 9 without a face/ten. It ties a Natural 9 (two card 9 w/ face/ten), but otherwise pays 3:2. However, Lucky 9′s after splits only pay even-money, and push against all dealer 9′s. The house edge of the game is 1.18%.
Probably, the only point of playing this game would be to see how confused the dealer gets when resolving hands involving Lucky 9, especially after split, or against a dealer Natural 9. I’m sure they’ll probably let you hit some hands after splits too. And people will think you’re crazy for standing on 5′s and 6′s.
Rules
The rules for Lucky 9 are as follows:
- Bets are placed before the hand is dealt.
- Player and dealer each receive 2 cards; the dealer upcard is exposed.
- The player may split pairs (up to 3 times) by matching the initial wager. Split hands receive only one card.
- The player may hit any non-split hand once, or stand.
- After the players action is complete, the dealer turns up his hole card.
- The dealer hits once on totals of less than 5.
- A non-split Lucky 9 (2-card 9 w/o 0-value card) pays 3:2, except for pushes against a dealer 2-card 9.
- A dealer Lucky 9 beats a player 3-card 9.
- All other player 9′s vs. dealer 9′s push.
- The player automatically loses with a total of 0, 1, or 2.
- Otherwise, wagers are resolved by comparing hand point totals.
Basic Strategy
I put the rules into my blackjack analyzer, and came up with a house edge of 1.18%, and the following auto-generated strategy:
| Hand | Dealer Upcard | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | A | |
| 2-Card Totals | ||||||||||
| 6-9 | S | S | S | S | S | S | S | S | S | S |
| 5 | S | S | S | S | H | H | H | H | S | S |
| 0-4 | H | H | H | H | H | H | H | H | H | H |
| Pairs | ||||||||||
| A-A | H | H | H | H | H | H | H | H | H | H |
| 10-10 | P | P | H | H | H | H | H | H | P | P |
| 9-9 | S | S | S | S | S | S | S | S | S | S |
| 8-8 | S | S | S | S | S | P | S | S | S | S |
| 7-7 | P | P | P | P | P | P | H | H | P | P |
| 6-6 | P | P | P | P | P | H | H | H | P | P |
| 5-5 | P | P | P | P | H | H | H | H | P | P |
| 4-4 | S | S | S | S | S | S | S | S | S | S |
| 3-3 | S | S | S | S | S | S | S | S | S | S |
| 2-2 | H | H | H | H | H | H | H | H | H | H |
The EORs for the game are extremely low compared to blackjack. There’s no value in counting this game.
Lucky 9 Bonus
The Lucky 9 Bonus is a side bet on your first 2 cards and the dealer upcard. The bet pays for various 3-card totals of 9, as listed in the paytable below. The house edge for this side bet is 13.1%. The EORs (sensitivities to card removal) are too low, and the initial house edge is too high, to make the side bet very countable. An ideal counter (using perfect knowledge of shoe composition) will find +EV betting opportunities about 2.7% of the time, with an average +10.8% EV/bet.
| Hand | Payout | Combinations | Probability | Return |
|---|---|---|---|---|
| Suited 3-3-3 | 200 | 224 | 0.000019 | 0.003761 |
| Suited 2-3-4 | 100 | 2,048 | 0.000172 | 0.017193 |
| Any 3-3-3 | 50 | 4,736 | 0.000398 | 0.019879 |
| Any 2-3-4 | 40 | 30,720 | 0.002579 | 0.103155 |
| Suited 9 Total | 30 | 70,144 | 0.005888 | 0.176653 |
| Other 9 Total | 5 | 1,070,592 | 0.089874 | 0.449369 |
| nothing | -1 | 10,733,696 | 0.901071 | -0.901071 |
| Total | 11,912,160 | 1.000000 | -0.131061 |
7 Up Baccarat @ Marina Bay Sands, SG
In today’s Grail quest, I took a look at the countability of a Baccarat variant called 7 Up Baccarat, dealt out of a constant shuffle machine (CSM). If you’ve read this blog closely, you know that a CSM does not eliminate all countability in a game. This is because cards are in buffered in the exit chute of the CSM, so recently dealt cards have no chance of coming out soon. A windowed count may be effective against a CSM.
You can browse or download all the code for this post, if you want to see how I roll.
Anyway, here’s what I found for 7-Up Baccarat. Both the banker and player bets have very high sensitivities to removed cards (EORs). (Compare this to normal baccarat, where the EORs are effectively zero.) Simulations show a windowed count is strongly correlated to the EV of the next hand dealt out of the CSM. The figure below shows a 20-card windowed count tells you when its better to bet Player or Banker. Unfortunately, the count almost never gets good enough to be +EV. You can see if they made the game more “fair” (house edge only 1.3% instead of the chosen 2.6%), then you’d often find some +EV opportunities. I doubt they did this kind of analysis, but who knows.

Same thing with the Super-7′s side bet. If they made the nominal house edge closer to 5% than the 8.9% they chose, then it’d be very countable. The count is very simple. Any 7 you see is -12, and any non-7 is +1. I think everyone can imagine that it’s better to bet the Super-7′s when they haven’t seen any 7′s out of the CSM in the last few hands. And I’m sure no one bets Super 7′s just after seeing a bunch of 7′s come out. Simulation of the Super-7′s bet show a perfect linear correlation between the count and the EV of the bet. In all simulations, a minBufferDepth of 20 was used (minimum number of cards in the exit chute buffer).

Power98 Baccarat @ Marina Bay Sands, SG
A few months ago, a reader contacted me about the ridiculously beatable Banker/Player Natural 8/9 bets in the Power98 Baccarat game at the Marina Bay Sands in Singapore. They used to pay 10:1 on a Natural 9, and 11:1 on a Natural 8. (And, they’d pay even more on a “Power Hand”.) Needless to say, this was obviously way too countable, and they finally figured it out, and lowered the pays down to 8:1 for both bets. This game was so beatable, I was even thinking about taking a trip out there. Oh well, our reader tells us that players figured it out, followed by management, and now it’s gone. I mean, this one was old school beatable. Throp and Walden wrote about this one in 1966, and that’s with a payout of 9:1 for both bets. What were these Power98 guys thinking? Anyway, even with their dealing procedure of placing 2 decks behind the cut card, the game was still beatable for about 61% of a fixed bet per shoe. It must have been funny to see everyone all of a sudden betting huge on both Player and Banker Natural 9. Oh well, sic transit gloria.
Dragon-7 Shoe Simulator
Click on the screenshot below to run my shoe-by-shoe simulator for counting the EZ-Baccarat Dragon-7 side bet:
I’ve been playing the EZ-Baccarat lately, because it’s really easy to count for the 40-to-1 Dragon-7 side bet, and it gets pretty exciting when you’re betting for big payouts at the end of a shoe (each $10 pays out $400). I’m still a baccarat newbie, but I’m starting to appreciate the drama of the game. Most people record notation of the hands, and they all study the hand history displayed on the monitor. They’re looking for long runs of Banker or Player wins. On a Banker run, they increase their bets, and everyone makes a lot of money, and all are happy. When the Player is on a winning run, they wait until they think it’s impossible for the Player to win yet another hand. Then they bet big on the Banker. If the Player wins again, everyone is outraged, and they bet even more to win back their money. It gets pretty dramatic, especially when the Player wins yet again. People don’t think like this on blackjack, probably because there’s no hand history display, and because you can’t bet on the dealer. Baccarat is a very dangerous game that feeds off of people’s natural instincts to see patterns in nature.
Anyways, I don’t care at all about Player/Banker, I’m just tracking the Dragon-7 count, and waiting for the opportunity to bet it. Mostly, this comes at the end of the shoe, so I make minimum Player or Banker bets just to feel a part of the table. Overall, betting $10 Banker/Player every hand will cost an average $8/shoe. I make $10+ dragon bets when the count is good, so I’ll win back at least $5.30/shoe of that on average. Overall, it’s very cheap entertainment.
I use the baccarat recording cards provided by the casino to track the dragon. Everyone uses the cards in Landscape orientation, and draws red and blue circles. I turn the card 90° and write down the +/- running count for each hand. I use the unbalanced Dragon-7 count, starting the RC at -32, and updating it for every card seen, including the burn. When the RC is greater than 0, I bet the dragon on the next hand.
My Flash game simulates one shoe at a time, showing the unbalanced running count (RC) that I record on the baccarat cards. I indicate the outcome of +EV dragon bets with green for wins, and red for losses. When a dragon occurs while not betting, I note the “miss” in yellow. For example, in the screenshot above, 83 hands were played in the shoe, and 3 dragons hit (hands #41, #67, and #69). The count wasn’t good enough to bet on the first dragon, which we missed (yellow). The RC was > 0 for almost all of the hands from #61 – #75. We hit the dragon on hand #67 when the count was +7, and on hand #69 when the count was +8.
Play around with the simulator if you’re thinking about trying to make a profit at the bet. While it’s probably the best +EV game you’ll ever find (easiest to implement, and most average profit per shoe), the game is very slow at a full table. In order to try to make money, you’d need to get heads up with a dealer, which can yield up to 3 shoes an hour (optimal). Needless to say, the swings are huge, due to the nature of the 40-to-1 payout. However, (2 shoes/hr)($100 dragon bets)(0.53 profit/shoe) = $100 profit/hr looks pretty attractive.
Panda-8 Bonus Bet @ EZ Baccarat
Read all my posts on the Panda-8 sidebet.
There’s another bonus bet on the EZ Baccarat table, called Panda-8, that pays 25-1 for a 3-card player 8 win. Using the same methods as the prior posts on countable baccarat side bets, I came up with the following card count values:
| Card | Count Value |
|---|---|
| Ace | 1 |
| Deuce | 1 |
| Trey | -2 |
| Four | -2 |
| Five | -2 |
| Six | -1 |
| Seven | -1 |
| Eight | -2 |
| Nine | 4 |
| Ten/Face | 1 |
The player should bet the Panda-8 when the true count is ≥ 11. (The plot below shows the EV curve crosses the x-axis at a true count of 10.5):

Use the following running count (RC) thresholds when betting the Panda-8 side bet:
| Hand # | RCMin |
|---|---|
| 55 | 31 |
| 56 | 29 |
| 57 | 28 |
| 58 | 27 |
| 59 | 26 |
| 60 | 25 |
| 61 | 24 |
| 62 | 23 |
| 64 | 21 |
| 65 | 20 |
| 66 | 19 |
| 67 | 18 |
| 68 | 17 |
| 69 | 16 |
| 70 | 15 |
| 71 | 14 |
| 72 | 13 |
| 73 | 12 |
| 74 | 11 |
| 75 | 10 |
| 76 | 9 |
| 77 | 8 |
| 78 | 6 |
| 79 | 5 |
| 80 | 4 |
| 81 | 3 |
| 82 | 2 |
| 83 | 1 |
| 84 | 0 |
Using the above RCmin thresholds, simulations showed a profit of 22% of a fixed bet per shoe, at an average 3.8 bets/shoe.

1 comment