What is the difference between fast and slow stochastic?

Slowing. With slowing set to 1 you get the raw %K — the 'fast' stochastic, which is very noisy. MT5's default of 3 smooths %K before %D is taken, which is what most traders mean by 'the' stochastic. There is no separate indicator; it is one parameter.

Stochastic or RSI — which should I use?

They measure different things. RSI compares the size of gains to losses; Stochastic compares the close to the recent high–low range. Stochastic reacts faster and gives more signals, which helps in ranges and hurts in trends. Neither replaces the other, and using both usually just gives you two versions of the same opinion.

Why does Stochastic stay pinned at 80 for so long?

Because in a trend the close genuinely keeps landing near the top of the range — that is what the indicator is reporting, and it is correct. Reading a pinned oscillator as 'due for a reversal' inverts what it says. Pair it with a regime filter before fading anything.

Does Stochastic have an applied-price setting?

Not in the usual sense. iStochastic takes a price-field selector instead: STO_LOWHIGH uses highs and lows, STO_CLOSECLOSE uses closes only. It also takes an ENUM_MA_METHOD for the smoothing. MT5's default, and the Builder's, is STO_LOWHIGH.

Can I build a Stochastic EA without coding?

Yes for level rules, %K/%D crossovers and centreline crosses — all three are a Stochastic node plus a Compare or Cross node, with periods and levels exposed as EA inputs. Divergence is the exception: it needs multi-bar swing detection the node palette does not cover.

How should I validate settings before going live?

Backtest on quality tick data first, then run the EA on a demo account before risking money. When optimising, hold back data the search never saw and prefer settings that stay profitable across periods over the single in-sample peak — chasing that peak is overfitting the noise. No default or preset here is a performance promise; every value is a starting point to re-validate on your own pair and broker.

Osciladores MomentumMean ReversionCrossover Disponible en Builder

Stochastic Oscillator

Stochastic

The Stochastic Oscillator shows where the close sits inside the recent high–low range, on a bounded 0–100 scale. It reacts faster than RSI and carries its own signal line, which makes both level rules and crossover rules straightforward to wire into a no-code EA.

Default settings: 5 / 3 / 3
Common levels: 80 / 20
Indicator range: 0–100

Crear en Builder Receta de estrategia

Ilustrativo — datos sintéticos, no una cotización en vivo.

What Stochastic tells you

Stochastic asks a narrow question: within the last K bars, did this bar close near the top of the range or near the bottom? A reading near 100 means closes are clustering at the highs, which is a statement about persistence, not about a reversal being due.

Above 80: closes are pinned near the top of the range
Below 20: closes are pinned near the bottom
%K crossing %D marks the moment that pressure changes hands

1 Find the high–low range of the last K bars
2 Locate the close inside that range
3 Smooth to get %K, then average it to get %D

Mostrar la fórmula y detalles de cálculo

Stochastic locates the close inside a recent range and then smooths the result twice:

Over the last K bars, find the highest high and the lowest low.
Express the current close as a percentage of that range: raw %K = 100 × (Close − Lowest Low) / (Highest High − Lowest Low). A close at the top of the range gives 100, at the bottom gives 0.
Apply the slowing average to raw %K. The result is MAIN_LINE, buffer 0 — what MT5 draws as %K.
Average %K over the D period to get SIGNAL_LINE, buffer 1 — the dotted %D line.

Because the denominator is the range itself, the reading is bounded to 0–100 and adapts automatically to volatility: the same 40-pip move gives a different number in a wide range than in a narrow one. That is also the indicator’s weakness — in a strong trend the range keeps shifting with price, so the close stays near the top and the reading stays pinned.

In MQL5 the call is iStochastic(symbol, period, Kperiod, Dperiod, slowing, ma_method, price_field). Note the last argument: it is a ENUM_STO_PRICE field selector (STO_LOWHIGH or STO_CLOSECLOSE), not an ENUM_APPLIED_PRICE. George Lane popularised the oscillator in the 1950s.

Señales

Las señales distintivas y testeables que ofrece Stochastic — y el régimen adecuado para cada una.

Overbought / Oversold

Listo en Builder

Condición: %K moves above 80 or below 20
Mejor régimen: Ranging markets
Uso típico: Fade the extreme — with a range or band filter

%K / %D Crossover

Listo en Builder

Condición: %K crosses its signal line
Mejor régimen: Turning markets
Uso típico: Time the entry more precisely than the level alone

Centreline Cross

Listo en Builder

Condición: %K crosses the 50 line
Mejor régimen: Trending markets
Uso típico: Flip momentum bias without waiting for an extreme

Divergence

Lógica avanzada

Condición: Price makes a new extreme, %K does not
Mejor régimen: Trend exhaustion
Uso típico: Anticipate a stall before price confirms

Implementación en MT5

Lo que MetaTrader 5 calcula y dibuja realmente: la referencia de cada regla de esta página.

Búferes

Índice	Búfer	Dibujado en MT5 como	Qué contiene
0	MAIN_LINE	Line	%K — where the close sits in the high–low range of the last K bars, after the slowing average is applied.
1	SIGNAL_LINE	Dotted line	%D — a moving average of %K over the D period. This is the line %K crosses.

Notas de la plataforma

Función MQL5

iStochastic

Precio aplicado

Este indicador no recibe argumento de precio aplicado.

En el Builder

iStochastic takes no ENUM_APPLIED_PRICE. Instead it takes a price field selector — STO_LOWHIGH (highs and lows) or STO_CLOSECLOSE (closes only) — plus an ENUM_MA_METHOD for the smoothing. The Builder's Stochastic node uses STO_LOWHIGH, the MT5 default.

Notas de implementación

iStochastic publishes %K on buffer 0 and %D on buffer 1 of the same handle, so a %K/%D crossover rule is two Stochastic nodes set to Main and Signal feeding a Cross node.
The Builder's Stochastic + Bollinger template reads %K only and compares it to a fixed level — the levels live in the Compare node, not in the indicator.
Divergence needs swing-high/low detection across several bars, which the node palette does not express; that signal requires custom MQL5.

Funciona mejor / usar con cuidado

Ningún indicador tiene ventaja universal. Aquí es donde Stochastic ayuda — y donde engaña.

Funciona mejor

Ranging markets
With a band or channel filter
Short-horizon entries
On liquid pairs with tight spreads

Usar con cuidado

Strong one-way trends
Fast settings on low timeframes
Levels as standalone entries
Optimised K/D pairs without validation

Crear una estrategia Stochastic

Conecta la señal a las reglas de entrada y salida, luego exporta un EA MT5 compilable — sin código.

Stochastic %K (5 / 3 / 3)
%K below 20 and price at the lower Bollinger band → Open Buy · SL 30 / TP 60
%K above 80 and price at the upper band → Open Sell

Combinar Stochastic con otros indicadores

Un indicador raramente se sostiene solo. Estas combinaciones cubren los puntos ciegos de Stochastic.

Stochastic + Bollinger Bands

%K < 20
Price at lower band
Buy

Por qué: Require price to be statistically stretched at the same moment the oscillator is extreme, so one condition has to agree with the other
Mejor régimen: Ranging

Crear esta estrategia →

Stochastic + ADX

ADX < 20
%K < 20
Buy

Por qué: Suppress the fade while a real trend is running, which is exactly when Stochastic pins at an extreme and stays there
Mejor régimen: Range filtering

No single-flow template pairs Stochastic with ADX. Start from Stochastic + Bollinger and add an ADX node with a Compare below 20 into the And gate.

Abrir el Builder →

Stochastic + Moving Average

Price > MA
%K crosses up through 20
Buy

Por qué: Take oscillator signals only in the direction of the higher-timeframe trend, so an extreme never becomes a counter-trend entry
Mejor régimen: Trend continuation

No single-flow template pairs Stochastic with a moving average. Add an MA node and a Price node into a Compare, gated with And ahead of the entry.

Abrir el Builder →

Stochastic + RVI

%K < 20
RVI main crosses above signal
Buy

Por qué: Both publish a main and a signal line and both are read on the crossing, but they measure the close against different things — Stochastic against the high and low of the last n bars, RVI against the open of the bar it closed in. A market can sit at the bottom of its recent range while its individual bars have started closing strongly, and requiring both to turn is a way of asking for that agreement explicitly
Mejor régimen: Ranging

No single-flow template pairs them. Start from Stochastic + Bollinger and replace the band condition with two RVI nodes at the same period — one set to Main, one to Signal — joined by a Cross.

Abrir el Builder →

Parámetros

Valores iniciales para validar en tu propio par y temporalidad — no son configuraciones garantizadas.

Parámetro	Valor predeterminado	Rango de prueba sugerido	Qué hace
%K period	5	5–21	How many bars the high–low range is measured over. The MT5 default of 5 is fast; 14 is the common slower alternative.
%D period	3	3–9	Averaging period that turns %K into the signal line. Larger means later but cleaner crossovers.
Slowing	3	1–5	Extra smoothing applied to %K before %D is taken. Slowing 1 is the 'fast' stochastic; 3 is MT5's default and is what most people mean by the indicator.
Overbought / Oversold	80 / 20	70–90 / 10–30	Your levels, not indicator inputs — iStochastic has no threshold argument. Move them together unless you deliberately want an asymmetric rule.

Ajustes preestablecidos iniciales

MT5 default 5 / 3 / 3 Fast, many signals

Classic slow 14 / 3 / 3 Fewer, steadier signals

Smooth 21 / 5 / 5 Swing-level readings only

Ejemplos de mercado

Dónde Stochastic funciona, dónde falla y cómo un filtro cambia el resultado.

Funciona

Fade in a range

In a sideways market %K drops under 20 while price sits at the lower band, and the move back toward the middle plays out — the case the template describes.

Falla

Pinned in a trend

In a strong move %K sits above 80 for bar after bar. Selling each overbought print fights the trend and pays the spread every time.

Filtrado

Filtered by regime

Add a trend-strength filter and the same run of extremes is ignored while price keeps trending — the filter is what makes a fade survivable.

Indicadores relacionados

RSI Ver guía →

Williams %R Ver guía →

Bollinger Bands Ver guía →

RVI Ver guía →

FAQ

What is the difference between fast and slow stochastic?: Slowing. With slowing set to 1 you get the raw %K — the 'fast' stochastic, which is very noisy. MT5's default of 3 smooths %K before %D is taken, which is what most traders mean by 'the' stochastic. There is no separate indicator; it is one parameter.
Stochastic or RSI — which should I use?: They measure different things. RSI compares the size of gains to losses; Stochastic compares the close to the recent high–low range. Stochastic reacts faster and gives more signals, which helps in ranges and hurts in trends. Neither replaces the other, and using both usually just gives you two versions of the same opinion.
Why does Stochastic stay pinned at 80 for so long?: Because in a trend the close genuinely keeps landing near the top of the range — that is what the indicator is reporting, and it is correct. Reading a pinned oscillator as 'due for a reversal' inverts what it says. Pair it with a regime filter before fading anything.
Does Stochastic have an applied-price setting?: Not in the usual sense. iStochastic takes a price-field selector instead: STO_LOWHIGH uses highs and lows, STO_CLOSECLOSE uses closes only. It also takes an ENUM_MA_METHOD for the smoothing. MT5's default, and the Builder's, is STO_LOWHIGH.
Can I build a Stochastic EA without coding?: Yes for level rules, %K/%D crossovers and centreline crosses — all three are a Stochastic node plus a Compare or Cross node, with periods and levels exposed as EA inputs. Divergence is the exception: it needs multi-bar swing detection the node palette does not cover.
How should I validate settings before going live?: Backtest on quality tick data first, then run the EA on a demo account before risking money. When optimising, hold back data the search never saw and prefer settings that stay profitable across periods over the single in-sample peak — chasing that peak is overfitting the noise. No default or preset here is a performance promise; every value is a starting point to re-validate on your own pair and broker.

Glossary

Términos clave

Sobreajuste Backtest Spread