Boom and Crash Spike Detector MT5: Free Download Guide

The promise that draws traders to spike detectors

You have seen the screenshots. A Boom chart, a sudden vertical candle, and a label that says the spike was called early. You want that move. You want the alert before the spike, not the chart after it. So you search for a Boom and Crash spike detector for MT5, download a file, and hope the next alert pays.

This guide is about what that file can and cannot do. It is written for traders who already know the basic idea of a synthetic index and want a straight answer on whether a detector is worth installing. The short answer is that a detector can help you watch a market more carefully. It cannot forecast the spike, and it cannot protect a stake that is too large.

The reason this matters is simple. Spike markets are designed to produce long quiet stretches followed by sudden jumps. A tool that counts those quiet stretches will always look useful after a jump, because the jump is the thing it was waiting for. The question is whether the count gives you an edge you can measure over time. Most traders never measure it, and that is where the losses begin.

What it costs to trust a spike alert you cannot audit

Consider a composite trader drawn from common forum stories. Call him Tomas. This is an illustrative composite, not a named person. Tomas installs a free detector, sees three spikes called correctly during one afternoon, and decides the tool works. He moves from a demo account to a small live account and sizes his trades as if each alert were a sure thing.

The following week, the alerts keep firing while the market keeps running in one direction. Tomas adds stakes to recover losses, and by Friday the account has lost most of its value. He did not break any rule he knew about. He simply never tested how long a losing run could last, never logged the alerts that failed, and never set a limit on how much he would risk in a single day.

That is the cost of a tool you do not measure. An alert feels like information, but on a synthetic index it may only be a count of ticks. Without a record, you cannot tell the difference between a useful signal and a comforting pattern.

What Boom and Crash indices are

Boom and Crash are names used for synthetic indices offered by some online brokers. Deriv is the best-known provider of this family of products. Deriv describes its synthetic indices as simulated markets generated by an algorithm. They are not tied to a stock exchange, a currency pair or an economic release.

The naming reflects the behaviour. A Boom index tends to move gradually and then produce upward spikes. A Crash index tends to drift and then produce downward spikes. Between spikes, the price usually moves in a fairly steady pattern in the opposite direction to the spike. That pattern is the reason spike trading is so hard: most of the time, the trade that would profit from the spike is losing money while you wait for it.

Why the algorithm matters

Because the index is generated by a rule set rather than by real trading activity, the detailed timing of each spike cannot be read from news or from the economy. A detector can only look at the ticks already produced. If the generator is designed so that past ticks do not reveal the next spike’s timing, then no indicator built on past ticks can reliably forecast the spike.

This is not a judgement about any one provider’s integrity. It is a description of how the product is built. Read the provider’s own product information before you trade, and treat anyone who claims a fixed schedule for spikes with suspicion.

How spikes are usually described

Traders often describe a spike in terms of an average number of ticks between spikes. That average is a property of the index as designed. It describes a long-run pattern, not a clock. A stretch that is longer than average may still continue for many more ticks, and a stretch that is short may end without warning. Averages are useful for planning, but they are not a countdown.

What a spike detector indicator actually does

A spike detector is a small program that runs inside MetaTrader 5 and reads the ticks on the chart you attach it to. It applies rules and draws a mark, a line or an alert when those rules fire. In most builds, the rules count how long it has been since the last spike, measure how quickly price has moved recently, and look at a few standard readings such as momentum and moving averages.

When the count passes a threshold, the detector may show an arrow or sound an alert. That alert says the rules have fired. It does not say a spike is coming in the next tick, the next minute or the next hour.

What the detector can show you

• How many ticks have passed since the last spike.
• Whether recent price action looks unusually quiet or unusually fast.
• A simple momentum or volatility reading, depending on the build.
• An alert when your chosen rule fires, if the build includes one.

What the detector cannot show you

• The exact moment of the next spike.
• Whether the next spike will be upward or downward in a way you can rely on.
• Whether your stake will survive the losing ticks between spikes.
• Whether the broker’s execution, spreads and margin rules match the test you ran.

The difference between these two lists is the whole point of this guide. A tool that tells you how long it has been since a spike is useful for watching a market. A tool that claims to tell you when the next spike will hit is not describing a method you can test.

Why counting ticks is not the same as forecasting

Counting ticks since the last spike is a real calculation, and it is easy to build. Many traders assume that a long stretch without a spike means one must be due. That is the gambler’s fallacy, the belief that a random process must correct itself. In a process designed to be random, the chance of a spike on the next tick does not rise because the previous stretch was long.

You can see the trap in a simple example. Suppose the detector flags a stretch that has run well above the average. A trader sees the flag and places a trade expecting a spike. The spike does not arrive for many more ticks, and the trade loses steadily in the meantime. When the spike finally arrives, the trader remembers the win and forgets the losses before it. The tool did not forecast anything. It simply produced a flag that the trader treated as a promise.

For that reason, the honest way to read a counter is as a description of the market’s recent history. It can tell you where you are in a pattern. It cannot tell you where the pattern will go next.

The drawdown you should expect before you place a single trade

Drawdown is the fall from a balance peak to a later low. It is the number that tells you how much pain a strategy can cause before it recovers, if it recovers at all. On spike markets, drawdown is often large, because the trade that wins on the spike is usually the trade that loses between spikes.

Before any live use, work out the worst run you could face. Decide how many ticks a losing position could move against you before the next spike, given the index and the stake. Multiply that by the number of positions you would hold. Then ask whether your account could survive that run without you adding money. If the answer is no, the stake is too large, regardless of what the detector shows.

Keep a written limit on drawdown. A common practice is to stop trading for the day once the account has lost a fixed percentage from its starting balance for that day. Choose the number before you open the platform. Traders who wait until a bad afternoon to choose a limit almost always choose a looser one than they would have chosen calmly.

Testing a detector on demo, properly

A demo test is only useful if it includes the bad parts. Most traders run a demo for an afternoon, see several spikes captured, and conclude that the tool works. That is a sample too small to mean anything, and it hides the long stretches that cause the largest losses.

Set the test up in writing first. Choose the index, the timeframe, the session length and the stake size you would use live. Set a maximum number of trades per session. Decide what counts as an alert you would act on, and write that rule down. Then keep the rules fixed for the entire test.

Log every alert the tool produces, including the ones you ignored, with the time, the tick count shown, the direction, the outcome and the drawdown during the trade. Include at least several sessions where the market runs in one direction for long periods. A detector that looks good only in choppy sessions has not been tested against the stretches that cost the most.

A simple test checklist

• Record every alert, with time, tick count and outcome.
• Measure the longest losing run in trades and in money.
• Track the largest drawdown from peak balance during the test.
• Compare results with and without the detector over the same sessions.
• Check whether the alert ever repainted or moved after it fired.
• Stop the test and reset if you breach your own daily loss limit, and record that breach.

If the drawdown is larger than you can accept, or if you cannot keep the log without breaking your own rules, the test has already told you what you needed to know. Do not move to live money on the strength of a few winning sessions.

Risk rules that matter more than the alert

The alert is the least important part of spike trading. Your stake, your daily loss limit and your rule for adding to a losing position matter far more. A detector can make a losing session look better in your memory. It cannot change how much you lose on each trade.

Keep each trade small enough that the worst realistic run is survivable. Do not increase stakes to recover a loss, because the recovery trade is the trade most likely to go wrong. Decide the maximum number of trades per session before you start, and stop when you reach it, even if the chart looks promising.

It is also worth separating the platform from the strategy. A broker’s execution, the margin required, and the spread or commission all affect the result. Read the broker’s product information for each synthetic index you trade. Do not assume that a result on one index carries over to another, because each index has its own behaviour and its own spike rhythm.

Working through a drawdown calculation by hand

Numbers make the risk concrete, so work through one example before you commit any money. The figures below are illustrative arithmetic, not data from any broker or any detector. Replace them with the stake, the contract details and the account size shown by your own platform.

Imagine an account with a starting balance of 1,000 units of account currency. Suppose you risk 10 units on each position and you hold positions through a stretch where the market moves against you for a long run of ticks. Each position shows a floating loss that grows while you wait. If you hold five positions and each one drifts down by a few units per hundred ticks, the floating loss across the group can exceed the stake you planned for any single trade. The balance falls before any spike arrives, and that fall is the drawdown you have to survive.

Now add the detector’s alert to the same picture. The alert may fire during the long run, and a trader who treats it as a signal may open more positions while the first group is still losing. The floating loss grows again, and the balance falls further. By the time the spike arrives, the account may be well below where the plan assumed it would be, even if the spike pays on the trades that caught it.

The lesson is not that every spike trade fails. It is that the path to the win can be far more expensive than the win is profitable. Before you go live, calculate the worst run you can tolerate, then size your positions so that run leaves you with capital to keep trading. If the calculation says you cannot survive a realistic run, the tool is not the problem. The stake is.

Write the calculation down and keep it next to your log. Update it when you change the stake, the number of open positions or the index. A number you wrote in advance is far harder to ignore during a bad afternoon than one you only carry in your head.

How long quiet stretches shape the trade

Spike markets spend most of their time not spiking. That is the part beginners underestimate. The quiet stretch is not dead time. It is the period in which most of your losses happen, because most trades placed while waiting for a spike lose money until the spike finally arrives.

Think of the market as a long wait punctuated by sudden moves. A trader who enters early pays for every tick of the wait. A trader who enters late may miss the start of the move. Neither approach removes the wait, and a detector that counts the wait does not shorten it. It only tells you how long it has lasted so far.

This is why an honest test has to include the long waits. Record how many ticks each trade stayed open before the spike, and how far it moved against you during that time. Over a large sample, those numbers describe the real cost of the approach. A single good spike does not change them, and a single bad wait does not define them either. Only the full set of trades does.

Some traders try to avoid the wait by setting a fixed exit, closing any losing position after a set number of ticks. That rule limits the drawdown on each trade, but it also turns many spikes into losses, because the spike sometimes arrives just after the exit. Test the exit rule as carefully as the entry rule. An exit that cuts losses on most trades can still lose money overall if it closes the trades that would have paid.

Setting up a session without tilting your judgement

Session discipline matters more on spike markets than almost anywhere else, because the feedback is so fast. A single spike can make a poor plan look wise, and a single bad run can make a sound plan look broken.

Before you open the chart, write down three things: the maximum number of trades for the session, the maximum loss in money or percentage, and the single condition that would make you stop early. Keep the note visible while you trade. Traders who skip this step tend to decide their limits in the middle of a losing run, when they are least able to judge them calmly.

Start each session with a short review of the previous one. Read the log, look at the longest losing run, and note any alert you ignored that later paid. The review is not a search for a magic rule. It is a way of keeping your expectations honest. If a particular alert keeps producing losses in your records, the log will show it, and the log is the only evidence that should change your plan.

End each session on a fixed time, not on a fixed feeling. If you are winning, the urge to continue is strong. If you are losing, the urge to recover is stronger. Both urges push stakes up and discipline down. A fixed end time removes the decision from the moment of greatest emotion, and it protects the account from the afternoon that goes wrong.

Synthetic indices versus forex and gold

Many traders come to Boom and Crash from forex or gold, so the comparison is useful. Forex pairs and XAUUSD trade on real markets with real participants, news releases and a wide range of liquidity. Their moves can be large, but they respond to information the trader can read: rate decisions, inflation data, geopolitical events and session volume.

Synthetic indices do not respond to news. That removes one source of surprise, but it removes the information you would normally use to judge a trade. Your analysis is limited to the price history the generator has produced, and that history is designed to make the next spike hard to predict.

If you want a tool that you can test against real market behaviour, consider the gold indicators guide. It covers how the same checks apply to a market with real news and real liquidity, which makes it a useful contrast to spike markets.

Common mistakes with spike detectors

The same errors appear in almost every losing account that started with a spike tool. They are worth reading before you install anything.

• Treating the count as a timer. A long stretch is not a promise of a spike. Stop reading the counter as a schedule.
• Adding stakes after losses. Increasing size to recover a loss is the fastest way to turn a bad run into a broken account.
• Testing only the good sessions. A test that skips the long quiet runs understates the drawdown you will meet.
• Ignoring the platform. A file built for one platform may not run correctly on another. Confirm compatibility first.
• Running several detectors at once. Conflicting alerts create confusion, and confusion leads to impulsive trades.
• Trusting a screenshot. A chart image shows one moment the author chose to share. Only your own log shows the full history.

How to judge any free or paid detector

Free files are common, and paid versions are common too. Pricing varies, so this guide does not quote one. Use the questions below to compare any two options, and run the same demo test on both before you decide.

Question	A good answer	A warning sign
Who wrote it?	A named author with a traceable history	An anonymous file with no contact details
Can you read the logic?	Source code or a clear written rule set	Secret rules that cannot be inspected
Does it claim to forecast spikes?	It describes what it counts and admits what it cannot see	It promises the next spike or a fixed schedule
What is the licence?	A clear licence that allows your use	No licence, or terms that restrict use
Is there a test you can run?	A demo procedure you can repeat yourself	Results shown only as screenshots

A tool that passes these questions is not thereby profitable. It is simply easier to test honestly. The test still decides whether it is worth any money.

Where to go next on this site

If you are still choosing a tool, the top ranking page explains how we compare indicators and expert advisors, using criteria you can apply to any product, not only ours. It is a useful checklist before you commit to a download.

Traders often ask how other people have used a tool before they try it. The customer feedback page collects experiences from people who have used our products. Read the critical comments as closely as the positive ones, because the critical ones usually describe the drawdown.

If you decide to run a longer demo test that needs a stable environment, the VPS option keeps a platform running when your own computer is switched off. It does not make a detector more accurate, and it does not reduce the drawdown of any strategy.

What you get and what it does not do

Because this guide covers a category rather than one verified build, the table below describes what a typical free spike detector provides and what it leaves to you.

Item	What you typically get	What it does not do
Counter	Ticks since the last spike, shown on the chart	Predict when the next spike will arrive
Alerts	Arrow, sound or pop-up when a rule fires	Confirm that a trade will win
Volatility readings	A simple measure of recent movement	Forecast the size of the next move
Settings	A few adjustable inputs	Protect a stake that is too large
Documentation	Sometimes a short readme	Explain every failure mode
Support	Usually limited for free files	Stand behind results in live trading

In short, a spike detector gives you a count and some alerts based on the ticks already produced. It does not forecast spikes, it does not reduce drawdown, and it does not replace a written risk plan. Anyone who presents a detector as a forecast is describing a product you should not trust.

Before any live use, verify the file’s source, read whatever logic you can, record every alert in a demo test, measure the longest losing run, and decide your loss limits in advance. Those steps cost time, not money, and they are the only checks that tell you anything real about the tool.

Decide with the log, not the alert

A spike alert is a question the detector asks of the market, not an answer. Its usefulness depends on whether the situations it flags have led to results you can accept, after costs and after the long losing runs, in your own records.

Start on a demo account with a written plan. Log every alert. Measure the drawdown. Include the sessions where the market ran against you for hours. Keep stakes small enough that a bad run is a setback rather than a loss you cannot recover from. If the log supports the tool after that, you have learned something useful. If it does not, you have learned the same thing at no cost.

Trading synthetic indices is not about catching a spike you cannot see coming. It is about building a process you can measure, limit and repeat. Test the detector, test your own discipline, and only then decide whether any real money belongs in the account.