Is the volume in MT5 real volume?

On retail forex, no. There is no central exchange for spot FX, so the terminal reports tick volume — how many times the quote changed during the bar. It correlates with activity and is genuinely useful as a participation proxy, but it is a count of updates, not a quantity traded. MQL5 does define VOLUME_REAL for instruments where the broker supplies it, and iOBV accepts it, but the Builder's generated code passes VOLUME_TICK.

What period should I use for OBV?

There is no period. OBV is a running total with no averaging window, which is unusual and is the reason there is nothing to optimise on the indicator itself. The number you choose is the comparison distance — how far back you look to decide whether the total is rising — and that lives in your rule, not in iOBV.

Why can't I just use a threshold like 'OBV above 100,000'?

Because the value depends on where the chart's history starts. Load more bars and every OBV reading changes. Two terminals on the same pair can show totals that differ by orders of magnitude, so a fixed level is meaningless and will behave differently on your broker than in a backtest with different history depth.

How do I read OBV divergence in an EA?

You have to define it first. Divergence means the sequence of price extremes disagrees with the sequence of OBV extremes, which needs swing detection on both series and memory across many bars. The node palette expresses single-bar comparisons, so the slope check is buildable today and divergence needs custom MQL5.

Can I build an OBV EA without coding?

Yes, as a confirmation. The OBV Confirmation + Bollinger Breakout template places two OBV nodes — one at the current bar, one twenty bars back — compares them to establish direction, and requires that agreement before acting on a band break. The lookback distance and the band settings are all EA inputs.

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. Be aware that OBV's input is your broker's tick count, so results are more broker-dependent than for a price-only indicator — a backtest on one feed's tick data does not transfer as cleanly as usual. Hold back data the search never saw and prefer settings that stay profitable across periods.

On Balance Volume for MT5 traders

What OBV tells you

OBV keeps one running total. Every bar that closes higher adds that bar's volume; every bar that closes lower subtracts it. The idea is that participation should lead price — if the total keeps climbing while price stalls, buyers are still arriving. What it cannot tell you is how much was traded, because on most retail forex feeds the number being accumulated is a count of price changes, not a quantity.

Rising OBV: up-closing bars are carrying more volume than down-closing ones
Falling OBV: the reverse
The absolute value means nothing — only the direction does

1 Compare this close with the previous one
2 Add the bar's volume if up, subtract if down
3 Carry the running total forward

Show the formula & calculation detail

On Balance Volume is a running total with one rule per bar:

Compare this bar’s close with the previous bar’s close.
If it closed higher, add this bar’s volume to the total. If it closed lower, subtract it. If they are equal, leave the total alone.
Carry the result forward to the next bar.

OBV = OBVprev ± Volume, and that is the whole calculation. There is no period, no smoothing and no scaling, which is why the indicator has no settings to tune and why its output has no bounds.

The reasoning behind it is that volume should lead price: if the total keeps rising while price moves sideways, buying is being absorbed and the move is more likely to resolve upward. That reasoning depends entirely on the volume series meaning what it is supposed to mean. On an exchange-traded instrument it does. On a retail forex pair the terminal reports tick volume — the number of quote updates in the bar — so OBV there accumulates activity rather than money, and a burst of small updates counts the same as genuine size.

In MQL5 the call is iOBV(symbol, period, applied_volume) where period is the timeframe and applied_volume is VOLUME_TICK or VOLUME_REAL. There is no applied-price argument — the direction comes from comparing closes internally, and the only thing you choose is which volume series to accumulate. The Builder’s generated code passes VOLUME_TICK.

Signals

The distinct, backtestable signals OBV gives — and the regime each one suits.

Rising Against Its Own Past

Builder ready

Condition: OBV today is above its value N bars ago
Best regime: Trending or breaking out
Typical use: Require accumulation before acting on a directional signal

Breakout Confirmation

Builder ready

Condition: Price breaks a level while OBV is climbing
Best regime: Breakout
Typical use: Skip breaks that nothing is following

Divergence from Price

Advanced logic

Condition: Price makes a new extreme, OBV does not
Best regime: Trend exhaustion
Typical use: Warn that a move is running on fewer participants

OBV Trendline Break

Manual interpretation

Condition: A line drawn across OBV's own lows is broken
Best regime: Either regime
Typical use: A discretionary read of the flow's structure

MT5 implementation

What MetaTrader 5 itself computes and draws — the reference every rule on this page is written against.

Buffers

Index	Buffer	Drawn in MT5 as	What it holds
0	MAIN_LINE	Line	The running total itself. It has no upper or lower bound and no natural origin — the value depends on how far back the chart's history goes, so only its direction and its relation to its own earlier values carry information.

Platform notes

MQL5 function

iOBV

Applied price

This indicator takes no applied-price argument.

In the Builder

iOBV takes no applied-price argument at all — its third parameter is an ENUM_APPLIED_VOLUME, not a price. The Builder's OBV node therefore exposes only shift and timeframe, and the generated code calls iOBV with VOLUME_TICK.

Implementation notes

iOBV publishes one buffer and takes no period, so there is no setting to tune — the only choices are which volume series and which bars you compare.
Because the running total has no threshold, a rule cannot be written as a Compare against a constant. The template places two OBV nodes with shift 0 and shift 20 and compares them against each other, which is the only form that survives the value being arbitrary.
The Builder's generated code passes VOLUME_TICK explicitly, so an EA built here reads tick volume even on an instrument where the broker also supplies real volume.
Divergence — price making a new extreme while OBV does not — needs swing detection on two series at once, which the node palette does not express.

Works best / use carefully

No indicator is a universal edge. Here is where OBV helps — and where it misleads.

Works best

Confirming a breakout rather than initiating one
Instruments where the broker supplies real volume
Higher timeframes, where tick counts are less erratic
Comparisons against OBV's own recent values

Use carefully

Any absolute threshold on the value
Comparing OBV across instruments or brokers
Treating tick volume as traded volume
Divergence read by eye without a defined rule

Build a strategy with OBV

Wire the signal into entry and exit rules, then export a compilable MT5 EA — no code.

OBV read at the current bar
A second OBV node read 20 bars back
Compare the two — rising means accumulation
Price crosses the upper Bollinger band and OBV is rising → Open Buy · SL 50 / TP 150
Price crosses the lower band and OBV is falling → Open Sell
Stop then trails behind the recent swing

Combine OBV with other indicators

One indicator rarely stands alone. These pairings cover OBV's blind spots.

OBV + Bollinger Bands

Price crosses the upper band
OBV above its value 20 bars ago
Buy

Why: A band break says the market has left its recent range; OBV says whether anyone came with it, which is the difference between a breakout and a spike
Best regime: Breakout

Build this strategy →

OBV + Moving Average

Price above the EMA
OBV rising
Buy

Why: Take the direction from a trend line and use accumulation as the permission slip, so pullback entries only happen while flow still favours the trend
Best regime: Trending

No single-flow template pairs OBV with a moving average. Start from OBV Confirmation + Bollinger Breakout and swap the band cross for an MA node with a Compare against price.

Open Builder →

OBV + MFI

OBV rising
MFI below 20
Buy

Why: Read the same volume series two ways — OBV as an unbounded running total, MFI as a bounded 0–100 reading — so one supplies direction and the other supplies an extreme
Best regime: Either regime

No single-flow template pairs OBV with MFI. Start from OBV Confirmation + Bollinger Breakout and add an MFI node with a Compare at 20, replacing the band condition.

Open Builder →

OBV + Force Index

OBV above its value 20 bars ago
Force Index crosses above zero
Buy

Why: Both are built from the same tick volume, but OBV never forgets and Force Index barely remembers — the running total describes where flow has been accumulating for weeks while a short Force Index describes the last two bars. Reading the recent push against the longer accumulation separates a genuine resumption from a spike that runs against the flow
Best regime: Trending

No single-flow template pairs the two. Start from OBV Confirmation + Bollinger Breakout and swap the band cross for a Force Index node crossed against a Constant of 0 — Force Index has a zero to cross, which OBV does not.

Open Builder →

OBV + Chaikin Oscillator

OBV above its value 20 bars ago
Chaikin above zero
Buy

Why: Two running totals that disagree about how to credit a bar. OBV gives the bar's whole volume to whichever way it closed against the previous close; the A/D total behind Chaikin splits that volume by where the close sat inside the bar's own range. When they agree, the move both ended higher and closed strong; when they diverge, one of those two things did not happen
Best regime: Trending

No single-flow template pairs the two. Start from OBV Confirmation + Bollinger Breakout and swap the band cross for a Chaikin node compared against a Constant of 0 — Chaikin has a zero to compare against, which OBV does not.

Open Builder →

Parameters

Starting values to validate on your own pair and timeframe — not guaranteed settings.

Parameter	Default	Suggested test range	What it does
Applied volume	Tick volume	—	iOBV's only real argument besides symbol and timeframe. MQL5 accepts VOLUME_TICK or VOLUME_REAL, but the Builder's generated code fixes it to tick volume, which is the series retail forex feeds actually populate.
Period	—	—	There is none. Unlike almost every other indicator, OBV has no averaging window — it is a running total from the start of the loaded history, so there is nothing here to optimise.
Shift	0	0–30	Which bar back the node reads the buffer from. Because OBV has no threshold to compare against, two nodes at different shifts are the normal way to express 'is it rising' — that is exactly what the template does with 0 and 20.

Starting presets

Short lookback 10 bars Reacts within the session

Standard 20 bars The template's comparison distance

Regime 50 bars Describes the week's flow

Market examples

Where OBV works, where it fails, and how a filter changes the outcome.

Works

Break with flow behind it

Price clears the upper band and OBV is already well above where it sat twenty bars earlier — participation arrived before the break and continued after it.

Fails

Break on nothing

The same band break happens but OBV is flat or lower than it was. Price pokes through and falls back, which is the case the confirmation exists to filter.

Filtered

The confirmation blocks the trade

A cluster of band touches in a quiet stretch is skipped entirely because the running total never turns up, and the account avoids a series of small losses.

Related indicators

MFI View guide →

Bollinger Bands View guide →

Standard Deviation View guide →

Accumulation/Distribution View guide →

FAQ

Is the volume in MT5 real volume?: On retail forex, no. There is no central exchange for spot FX, so the terminal reports tick volume — how many times the quote changed during the bar. It correlates with activity and is genuinely useful as a participation proxy, but it is a count of updates, not a quantity traded. MQL5 does define VOLUME_REAL for instruments where the broker supplies it, and iOBV accepts it, but the Builder's generated code passes VOLUME_TICK.
What period should I use for OBV?: There is no period. OBV is a running total with no averaging window, which is unusual and is the reason there is nothing to optimise on the indicator itself. The number you choose is the comparison distance — how far back you look to decide whether the total is rising — and that lives in your rule, not in iOBV.
Why can't I just use a threshold like 'OBV above 100,000'?: Because the value depends on where the chart's history starts. Load more bars and every OBV reading changes. Two terminals on the same pair can show totals that differ by orders of magnitude, so a fixed level is meaningless and will behave differently on your broker than in a backtest with different history depth.
How do I read OBV divergence in an EA?: You have to define it first. Divergence means the sequence of price extremes disagrees with the sequence of OBV extremes, which needs swing detection on both series and memory across many bars. The node palette expresses single-bar comparisons, so the slope check is buildable today and divergence needs custom MQL5.
Can I build an OBV EA without coding?: Yes, as a confirmation. The OBV Confirmation + Bollinger Breakout template places two OBV nodes — one at the current bar, one twenty bars back — compares them to establish direction, and requires that agreement before acting on a band break. The lookback distance and the band settings are all EA inputs.
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. Be aware that OBV's input is your broker's tick count, so results are more broker-dependent than for a price-only indicator — a backtest on one feed's tick data does not transfer as cleanly as usual. Hold back data the search never saw and prefer settings that stay profitable across periods.

Glossary

Key terms

Backtest Overfitting Exponential Moving Average