Mar 20, 2017
Testing roulette system

Testing Roulette Systems - The Holy Grail System

The system, called the Holy Grail, is based on the assumption that numbers will not be repeated in the beginning and follows the principle that when unique numbers come up, these numbers have a higher chance of being repeated. Therefore you follow the numbers which have come up and when 18 unique numbers have been hit, you bet on them with one unit and you continue to play as long as you are making a profit. Then you reset stakes and you wait until 18 new unique numbers have been hit again.

What do the Statistics say?

Looking at that from the Statistics’ point of view the system is premised on betting on any 18 out of 37 numbers and on the basis of that we can assume that in the long term betting it should go below zero. Generally, the probability of winning in roulette is 18/37 = 48, 65%, and an expected profit is 48, 65*18-51, 35*18 = minus 48, 6 units per 100 spins. Well, let’s see this following test simulation per 20.000 spins:

Obviously, the progression went completely below zero as we had assumed. We observed a downward trend. We have attempted to apply a linear series progression. It meant that if we bet on certain numbers per every 20 spins and we did not reach a profit, so then we increased the bet size by one unit on each number. The outcomes are shown in the following graph:

According to our expectation, the graph resulted in the typical Martingale progression. Therefore this roulette system had an upward trend but huge local slumps were present and reached values of up to hundreds of thousands of units.

Sometimes a slump was so huge that the system was not able to go back and made a profit. For that reason there is no point in applying more aggressive progression, the progression would not be changed even if we would lengthen a period between progressions (we tested the system to 40 spins) and if we would shorten a period either (to 10 spins), the progression of this system was not changed. In this form the system was unusable.

Comments (0)
Add a comment

You have to be logged in to add a comment