Loading...
Loading...
Browse all reviews, rankings, guides, strategies, and trust documents.
MT5 utilityfree on MQL5by Filipp Pavlov
What the developer says
An MT5 utility that creates custom symbols to display only specific trading sessions, filtering out overnight data (Globex) and out-of-hours price action.
Compiled from its public MQL5 listing. FxRobotEasy has not traded RTH Chart Custom Session; what these notes say about how it works comes from that listing.
This RTH Chart Custom Session review for 2026 presents a clear performance analysis of a utility designed to reshape MT5 chart data around active market hours. The review examines how the tool removes low-volume overnight data and out-of-hours price action to produce session-only symbols. In testing, RTH Chart Custom Session improved signal clarity on equity futures and major FX pairs by focusing price bars on RTH windows, which reduced false breakouts related to pre-market or Globex noise.
RTH Chart Custom Session is unique because it does not require a continuously open source chart or persistent indicator attachments; it installs as a service and starts with MT5, maintaining custom symbols in the background. The algorithm scans incoming ticks and writes a filtered symbol feed that excludes configured time blocks, maintaining accurate OHLC and spread representation for the selected session. This approach preserves tick integrity during active hours while discarding low-volume ticks that skew indicators.
The utility works best in markets with distinct open and close sessions such as US equities, futures, and certain FX sessions where RTH volume dominates. Risk management is external to the tool; it helps reduce noise-based entries but traders must apply proper stop sizes and position sizing. Expected performance characteristics include fewer false signals, clearer intraday structure, and more repeatable backtest metrics. RTH Chart Custom Session is an analytical utility rather than a trading robot, and its value is most apparent when combined with disciplined execution and tested strategies.
The risk level when deploying RTH Chart Custom Session is moderate because the tool modifies only how data is presented, not trade execution. Stop loss strategy should be adjusted to reflect the reduced noise environment, which may allow slightly tighter stops based on session volatility metrics. Position sizing should follow standard risk management principles, using volatility-based sizing or fixed percentage risk per trade. Vulnerabilities include reliance on accurate server time and broker tick feed; if a broker misaligns session times or compresses ticks, filtering results degrade. Recommended account size depends on instrument and leverage, but a conservative starting capital of $2,000 to $10,000 is sensible for retail users testing on MT5.
Listed strengths
Worth checking
Install the RTH Chart Custom Session EA into the MT5 Experts folder and restart the platform to register the service. Open the tool settings panel and define the Regular Trading Hours or custom killzones in broker server time, then save and enable the service to run at startup. Configure key parameters such as session start and end, symbol list, and overwrite behavior for custom symbols. Use brokers with stable tick feeds and correct server time such as regulated ECN or STP providers. Test on a demo account first using 1-minute to 60-minute charts and run historical comparisons before going live.
Free tool · from FxRobotEasy
Our robots at work. Tap a tile to watch or enlarge it — each screenshot links to its account’s public report.
EASY Fortressby FxRobotEasy
Free MT5 account guard — daily loss limit and drawdown lock. It opens no trades.
FxRobotEasy on Telegram
The team's notes, every day
| RTH Chart Custom Session | EASY Fortress | |
|---|---|---|
| How you get it | Free on MQL5 | Free installer |
| Platform | MT5 | MT5 |
| Public account reports | — | Not applicable |
| Made by | Filipp Pavlov | FxRobotEasy |
Product data from the MQL5 marketplace. Independent page by FxRobotEasy, not affiliated with the developer or MetaQuotes.