LayTriGGer

Filed under: Previews |

LayTriGGer is, as you might guess, a laying system.  It has been on the market now for a good few months and, in fact, we were approached a few months ago by the author and asked to test it out.  For one reason or another, I didn’t get round to it and after a few more emails from Richard I thought I should get my finger out and get it tested.  I really like it when someone approaches us and requests we test their product.  It shows they have faith in it which is pretty confidence inspiring for me as a tester.

LayTriGGer comes in PDF format and is seven pages long.  There is a short introduction with a bit of history, a page of system rules, a page for staking advice, a page of previous performance and a couple of other info pages at the back.  All in all, a pretty concise guide.

LayTriGGer aims to lay certain horses in particular race types and is concentrated mainly around mid pack selections.  Because of this the odds are a little higher than I’d personally like, but if it’s as good as is claimed (averaging over £32000 in the last four years to £100 levels), then I could get over it :)

The system itself is fairly straight forward and it’s possible to complete four of the six rules the evening before, or morning of racing.  The last two rules (and a check of rule four) need to be carried out as near to the start of each race as possible, but with the aid of a bot (LayTriGGer recommend MarketFeeder Pro) this is easily overcome for those who can’t be at a PC during the day.

Because of the author’s persistence in asking us to test this, I’m quite excited about LayTriGGer, so time will tell if my excitement is justified.

There are two recommended staking plans, one is straight forward level stakes and the other utilises a mild loss recovery method.  For the trial, I’ll run two separate banks according to the recommended staking levels, one for level staking and the other using the staking plan and we can compare the two at the end of the test.  The levels will be a £2000 bank played at straight £20 stakes, and the staking plan bank will be a £4000 bank with a base stake of £20.

The results are posted below and followed up with a disappointing conclusion as you’ll read:

Results

Date Day No. Level Stake Staking Plan Total Level (£) Total Staking (£)
15-Nov 1 0 48.86 0 48.86
16-Nov 2 38 57 38 105.86
17-Nov 3 209 217.14 247 323
18-Nov 4 152 152 399 475
19-Nov 5 -38 -19 361 456
20-Nov 6 133 190 494 646
21-Nov 7 133 133 627 779
22-Nov 8 190 190 817 969
23-Nov 9 57 57 874 1026
24-Nov 10 -106 -87 768 939
25-Nov 11 -143 -197.57 625 741.43
26-Nov 12 95 203.57 720 945
27-Nov 13 -626 -1653.57 94 -708.57
28-Nov 14 133 494 227 -214.57
29-Nov 15 209 507.57 436 293
30-Nov 16 114 141.14 550 434.14
01-Dec 17 76 76 626 510.14
02-Dec 18 -38 10.86 588 521
03-Dec 19 -85 -59 503 462
04-Dec 20 57 97.26 560 559.72
05-Dec 21 95 111.28 655 671
06-Dec 22 171 171 826 842
07-Dec 23 38 38 864 880
08-Dec 24 -105 -69.71 759 810.29
09-Dec 25 152 192.71 911 1003
10-Dec 26 -296 -277 615 726
11-Dec 27 -318 -1037.71 297 -311.71
12-Dec 28 -162 -1888.15 -116 -2437.86
13-Dec 29 -106 -540.55 -268 -2979.41
14-Dec 30 76 461.43 -192 -2517.98

Conclusion

What can I say about LayTriGGer.  A system that started with so much promise, banking over 50 points profit in just over a week before taking a nosedive, recovering again, and then committing apparent system suicide by breaking the bank.

As it’s been a while, I’ll give you a quick summary of the system:  LayTriGGer is a fairly simple laying system, concentrating on selections in a certain range of the live betting.  It comes with a staking plan or is claimed to show considerable profit at level staking.  The author recommends using MarketFeeder Pro to place your bets and includes the settings required which is a great help to a technical numpty like me.

Onto the test then and, as I said above, it started in a blaze of glory, going on to bank over 50 points profit using the staking plan and not far off the same using level stakes, all within nine days.  We then took a bit of a hit with a series of selections going on to win their races.  At that point, I figured all was lost but was pleasantly surprised to see the bank recover well and indeed head back over the 50 point profit again.  It didn’t last long though as a few days later we started hitting those pesky winners again and, at mostly double figures, they were doing considerable damage to the staking bank especially.

Although I wrapped the site test up on the 14th December I continued it behind the scenes right up until the 31st December just to see if LayTriGGer could indeed recover again.  I’m sorry to report that it didn’t.  In fact worse than that the bank dipped so low that it wouldn’t have been possible to place the required bets.  Assuming you decided to top up your bank to cover bets, then at it’s worst, you’d have been left with just £55.71 of your initial £4000 deposit!  Another point to bear in mind that I was effectively playing with a £5000 bank due to my initial winnings, so if you’d started LayTriGGer when it hit it’s run of winning selections then you’d have been hammered much earlier.

So, I’m afraid it can be nothing less than a thumbs down for LayTriGGer, which is a shame when you consider what it achieved in it’s first week and a bit, but what it then when on to achieve is nothing less than disasterous.

Important Update:

It would appear that the author of LayTriGGer, known only as Richard,  has shut up shop and ‘done one’.  A real disappointment, but sadly not unheard of.  So, if anyone was considering buying LayTriGGer even after it spectacularly bombed right here on HR.ie then DON’T!

VN:F [1.9.17_1161]
Rating: 0 (from 0 votes)
Posted by on November 15, 2008. Filed under Previews. You can follow any responses to this entry through the RSS 2.0. You can leave a response or trackback to this entry

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>