Two Jackpots /one meeting.
- Dave Scott
-
Topic Author
- Administrator
-
- Posts: 43867
- Thanks: 3338
Two Jackpots /one meeting.
5 years 6 months ago
TAB MEDIA RELEASE
SUBJECT: Two Jackpots on one SA meeting daily
DATE: Thursday 21 November 2019
RELEASED BY: Phumelela Gaming
TAB will operate a second Jackpot pool on one South African race meeting daily from today’s race meeting at Fairview.
The second Jackpot will start on the race after the first leg of the normal Jackpot at race meetings comprising eight or nine races.
So, at an eight-race meeting, Jackpot ONE will be on races 4 to 7 as normal and Jackpot TWO on races 5 to 8.
In the case of a nine-race meeting, Jackpot ONE will be on races 5 to 8 and Jackpot TWO on races 6 to 9.
TAB customers must note that in order to play Jackpot TWO in Phumelela regions they must mark venue oval number 9 and the first-leg race number of Jackpot TWO.
TABGOLD customers in KwaZulu-Natal totes must mark the SPQ oval.
This is in order to ensure that will pays for both Jackpot pools on a meeting can be displayed correctly.
So, in the case of Jackpot TWO at Fairview today, mark venue oval 9 (not E CAPE) and Race 5 to bet.
If there are two South African meetings on a day, Jackpot TWO will be offered on the race meeting likely to attract the biggest pool.
SUBJECT: Two Jackpots on one SA meeting daily
DATE: Thursday 21 November 2019
RELEASED BY: Phumelela Gaming
TAB will operate a second Jackpot pool on one South African race meeting daily from today’s race meeting at Fairview.
The second Jackpot will start on the race after the first leg of the normal Jackpot at race meetings comprising eight or nine races.
So, at an eight-race meeting, Jackpot ONE will be on races 4 to 7 as normal and Jackpot TWO on races 5 to 8.
In the case of a nine-race meeting, Jackpot ONE will be on races 5 to 8 and Jackpot TWO on races 6 to 9.
TAB customers must note that in order to play Jackpot TWO in Phumelela regions they must mark venue oval number 9 and the first-leg race number of Jackpot TWO.
TABGOLD customers in KwaZulu-Natal totes must mark the SPQ oval.
This is in order to ensure that will pays for both Jackpot pools on a meeting can be displayed correctly.
So, in the case of Jackpot TWO at Fairview today, mark venue oval 9 (not E CAPE) and Race 5 to bet.
If there are two South African meetings on a day, Jackpot TWO will be offered on the race meeting likely to attract the biggest pool.
Please Log in or Create an account to join the conversation.
- Deeno
-
- Platinum Member
-
- Posts: 8174
- Thanks: 483
Please Log in or Create an account to join the conversation.
- Thor
-
- Platinum Member
-
- Posts: 2783
- Thanks: 468
Re: Two Jackpots /one meeting.
5 years 6 months ago
What they should do is make a jackpot where you can select any 4 legs from the last 6 to be your legs. Similar concept to the soccer any 15 bet. This will surely be a hit.
I take my payment for the idea by EFT thanks.
I take my payment for the idea by EFT thanks.
Please Log in or Create an account to join the conversation.
- MissT
-
- Premium Member
-
- Posts: 596
- Thanks: 175
Re: Two Jackpots /one meeting.
5 years 6 months ago
Yeah but unfortunately the size of the cake remains the same just creating smaller slices imo.
The following user(s) said Thank You: Muhtiman, mr hawaii
Please Log in or Create an account to join the conversation.
- naresh
-
- Platinum Member
-
- Posts: 6385
- Thanks: 1497
Re: Two Jackpots /one meeting.
5 years 6 months ago
Having two Jackpots in a local meeting is a good idea but,
now you have a scenario that at times you going to have at least three legs being part of both the Jackpots, eg
Race 4, 5, 6, 7
Race 5, 6, 7, 8
In most instances you can go out of both the Jackpots simultaneously if you dont pick the winner of that leg that makes up both Jackpots.
My suggestion would have been the first four races of every meeting should have been the first Jackpot and the other Jackpot will remain as is.
now you have a scenario that at times you going to have at least three legs being part of both the Jackpots, eg
Race 4, 5, 6, 7
Race 5, 6, 7, 8
In most instances you can go out of both the Jackpots simultaneously if you dont pick the winner of that leg that makes up both Jackpots.
My suggestion would have been the first four races of every meeting should have been the first Jackpot and the other Jackpot will remain as is.
The following user(s) said Thank You: mr hawaii
Please Log in or Create an account to join the conversation.
- mr hawaii
-
- Platinum Member
-
- Posts: 20062
- Thanks: 2653
Re: Two Jackpots /one meeting.
5 years 6 months ago
Very soon there may well be a University course - Bet types on Racing - I must say I battle to keep up with all the changes - Thank god I'm not compulsive or I'd need Ritalin just to focus on all the different bets and rules for the different venues....
The following user(s) said Thank You: Muhtiman
Please Log in or Create an account to join the conversation.
- Frodo
-
- Platinum Member
-
- Posts: 13118
- Thanks: 3032
Re: Two Jackpots /one meeting.
5 years 6 months ago
I agree with Mr H that this constantly changing of bet types is not good - who is to say that after a few months they decide to do away with this again - as was the case with the 'rolling double'; surely do some market research first to see if an idea has a chance of working 
For me personally having a 2nd JP will help, as it covers another leg of the P6 - but I suppose it would depend on one's 'betting strategy'; as far as growing pools though, I don't think it will have much of an effect

For me personally having a 2nd JP will help, as it covers another leg of the P6 - but I suppose it would depend on one's 'betting strategy'; as far as growing pools though, I don't think it will have much of an effect
Please Log in or Create an account to join the conversation.
- Muhtiman
-
- Platinum Member
-
- Posts: 8928
- Thanks: 1014
Re: Two Jackpots /one meeting.
5 years 6 months ago
.....then its bye-bye P6 for me....will not increase my spend to get the last leg at 2nd JP end....:dry:
Please Log in or Create an account to join the conversation.
Time to create page: 0.117 seconds