• Not yet betfair user? Get your free bet.

    Take winnings early or cut losses. Cash Out singles and accumulators. You're in control - you decide. Automatically get the best prices from The Exchange the moment you place your Sportsbook bets. Win or lose, we'll match your first bet with a free bet up to £50.

  • Intuitive and Customizable User Interface

    Choose one of three user interfaces for your betfair trading. Create your application workspace for trading on ladders, or for betfair bot execution.

  • Quick Navigation and Browsing Through Betfair Markets

    Create your favourite events to browse quickly for markets you want to trade on. Searching, sorting and filtering is supported across the entire application on any data.

  • Support for Trading on Multiple Markets Simultaneously

    Monitoring odds trend for chosen market selections and watching for current profit on open bet positions. Possibility to close bet position on a market selection, on entire market or on all open bet positions.

  • Trading Tools and Betfair Bots, Support for Automated Trading

    Placing dutch bets, closing a bet position on selection or on entire market. Be the firts in queue, Tick offset, Drip feeding, Trading bots, Trailing stop loss and more than ten other betfair bots. Tools for automated trading and betfair strategies.

Welcome to betfair trading software.

Community Recent Articles

Community Recent Comments

  • Edumadrid
    11/26/2015 6:24:59 PM

    Why does not work this setting?

  • Stefan
    11/19/2015 6:09:33 PM

    Last days I had been working on racingpost data provider, you can see it in my test bot using spreadsheet.

    The racingpost data provider extends a set of data providers I developed before for some betfair bot projects: timeform, olbg, sportinglife.

  • Stefan
    11/14/2015 4:14:46 PM

    I have just released the latest version of bfexplorer adding PreviousSetGamesScore parameter.

    I renamed some parameters so change your bot settings to reflect new parameters. SetsScore and PreviousSetGamesScore parameters support multi value settings, used separator is ;

  • Stefan
    11/13/2015 12:58:29 PM

    For now the tennis bot supports two parameters SetScore and GameScore, only GameScore parameter is mandatory.

    GameScore defines current set score. What you suggest could have more general use if we introduce on which set the game score should be applied.

    So I would suggest using: PreviousSetGameScoreIndex parameter and PreviousSetGameScore parameter.

    What do you think about it?

  • Stefan
    11/8/2015 4:11:49 PM

    Eduardo, I do not know from which comment you started to follow that debate, but as you could maybe notice after 20 or so comments, all that was just chitchat. Why I call it chitchat? Because from what was said, I created two other articles with videos, and Ilya did not bother to comment that or mentioned it in his further debate.

    My conclusions:

    1) It is impossible that whenever someone from this forum will cooperate with other member to make anything which could be shared.

    2) The level of understanding of the base features any betfair trader needs to manage is very poor.

    3) I am sure now that right naming of essential features is very important. It is pity that on this forum there is actually no member now, who natively speaks English and would be willing to correct us all. For instance the name bot, from my understanding now it was unfortunate to call it bot, maybe order, rule, or something like that would be more appropriate. I already renamed “My Bots” view to: “My Orders/Bots to Execute”.

    Eduardo, your concern was subscription level and amount of features you can buy for your subscription, but you know that it was never a problem. Whenever someone asks me for Professional subscription for an amount he/she is willing to pay or donate I did/do so, but he/she should be at least an active bfexplorer forum user.

  • Stefan
    11/8/2015 4:11:08 PM

    Eduardo, I am sorry to hear that you lost some money just because you did not understand what staking plan you actually execute with your strategy and what maximal liability could be reached by your bot settings.

    I think you used some of bot triggers from My Staking Plan series, describing how to program a bot trigger with a custom staking plan:

    The staking plan was implemented by Eric’s requirements for his betting strategy:

    If there is a loss, double my stake and add previous loss to my stake.
    If there is a loss and my previous bets are in profits, then double stake only.
    If there is more than 3 consecutive losses then bet with default stake. 

    So the bot trigger implemented two parameters: Stake and NumberOfRecoveryBets. Depending on what betting strategy was executed, we do not know if his action bot placed back or lay bets on selected horses and at what average odds range, only he knew what could be his maximal labiality on his final bet placed at the recovery plan.

    Knowing what you actually do and what could be maximal liability bet when executing any staking plan is absolutely crucial for any successful strategy.

    The worst case scenario is when all goes well when testing and without aware of the risk you switch to execute your strategy with real money too soon. That is a price you paid to learn that you must test weeks and not days to test your strategy.

    Here are my answers to your original question:

    First of all, you already used a bot trigger with staking plan implementation, so if you wanted to add some stop criteria for your action bot, for instance when total target loss is reached then such criteria should be added to the bot trigger code.

    You tried to use “Execute Till Target Profit” bot setting the bot parameter: TargetProfit to -10.0 (minus ten), hoping that such bot setting will stop your action bot execution when loss is reached.

    Such settings cannot definitely work, and there 2 reasons why it cannot work.

    The bot implementation works only with profit, if bot would implement target loss then you could find it in bot parameters listing, for insistence the parameter would be named: TargetLoss.

    The bot checks if target profit is reached by comparing the current profit with the target parameter value. When current profit is bigger or equal to set target profit then action bot execution is stopped.

    In school we learned that zero or positivity value is bigger than any negative value, right? Even minus one is bigger than minus two, therefore your bot stopped action bot execution at first execution, as 0 is bigger than -10.

    I can update the bot: “Execute Till Target Profit” to work with a target loss in my next bfexplorer release.

  • Edumadrid
    11/6/2015 7:06:09 PM

     Hi Stefan:

    A few days ago I lost € 240 with a stake of 1 €, I used the robot "Lay favorite with my staking plan. -10"

    I had four straight losses and did not stop when the robot lost 10 €.

    Please, Stefan, how can I do so that the robot stops when it reaches the established loss?

    It would be possible to divide the bankroll into several parts and using only a part and if anything is unsettles, which lost only one of the parts and not all parts?

    Thanks in advance.

  • Stefan
    11/5/2015 1:09:59 PM

    Please translate to Spanish what it means “Entry Criteria”.

    Those parameters, if set then refer to the current market ProfitBalance, so your action bot will continue its execution only if current Profit Balance on the market is greater or equal 10, that means that on this market you already placed bets and your current profit balance is >= 10.

  • Stefan
    11/5/2015 1:02:18 PM

    It would be really great if you mention which bot you are using, and if you refer to some article on forum, then add link to this article.

  • Stefan
    11/5/2015 12:22:05 PM

    May I ask you to present us a video showing how you use this tool?

Bfexplorer Statistics