IBI Intermarket ZScore: MT5 indicator for standardized cross-market strength and signals

The IBI Intermarket ZScore review for 2026 focuses on performance and analysis of a relative strength indicator designed for MT5. IBI Intermarket ZScore measures how a chosen symbol deviates from a benchmark or driver list using statistical Z-Scores, which makes cross-market comparisons meaningful even when instruments have very different volatility profiles. In practical terms, the indicator converts price differences into standard deviations so traders see when a market is unusually strong or weak versus its peers. Fernando Augusto Poltronieri developed the indicator and offers it as a $99 MT5 tool with a 4.5/5 rating from 100 reviews on the marketplace. What makes IBI Intermarket ZScore unique is its direct handling of inverse relationships, ability to aggregate multiple drivers, and a normalization method that reduces false signals from volatility spikes. The algorithm computes normalized residuals over configurable lookbacks, flags threshold crossings, and optionally smooths outputs with moving averages to avoid whipsaw in thin markets. It performs best in markets with clear leadership rotation such as forex majors relative to USD indices, sector rotation in equities, and commodity spreads. Risk management is left to the trader, but the indicator includes recommended thresholds and settings to pair with stop loss levels and position sizing rules. Expected performance characteristics include improved signal-to-noise when used with confirmation, moderate trade frequency depending on timeframe, and clearer entry bias during trending and rotational market phases.

IBI Intermarket ZScore typically yields a moderate win rate when used as a confirmation filter rather than a standalone trigger. In backtests and live samples provided by users, win rates clustered between 52% and 65% depending on timeframe and asset class, with higher accuracy on daily and four-hour charts. Drawdown management is improved relative to raw price-based strategies because Z-Score thresholds filter trades made during volatility spikes; historical maximum drawdowns reported by users range from 6% to 15% on sample equity curves. Trade frequency varies with settings, from a few signals per month on daily charts to several dozen on hourly charts, so account sizing should reflect expected activity. Minimum recommended account sizes start at $1,000 for micro lots, scaling to $5,000+ for standard position sizing and robust risk controls. Timeframe considerations matter: the indicator produces cleaner signals on higher timeframes and should be combined with trend filters or volume confirmation on lower timeframes.

The risk profile for IBI Intermarket ZScore is moderate when used with conservative position sizing and explicit stops. Because the product is an indicator for MT5, stop loss strategies remain the trader's responsibility; users commonly pair Z-Score signals with fixed ATR-based stops or percentage stops to control risk. Position sizing should follow a volatility-adjusted model, allocating 0.5% to 2% of equity per trade depending on confidence and timeframe. The indicator is vulnerable during sudden regime changes, central bank events, or holidays when correlations break down and drivers behave erratically. For retail traders, a recommended starting account size is at least $1,000 for micro accounts and $5,000 for standard trading to absorb expected drawdowns and trade frequency.

Install IBI Intermarket ZScore by copying the indicator file into the MT5 Indicators folder and restarting the platform. Attach the indicator to the chart and select the benchmark symbol or enter a comma-separated list of driver symbols in the settings. Configure lookback period, smoothing, and Z-Score threshold values to match your chosen timeframe. Recommended brokers are low-spread, FIFO-compliant ECN or STP providers with reliable execution for cross-asset comparisons. Optimal chart timeframes are H4 and daily for primary signals, with hourly for supplemental entries. Backtest on a demo account for at least three months and forward-test with small size before live deployment.