Can some help in getting Supply and demand Zone indicators for MT5 ...Please share the link

[Udhaya Kumar]

Hi,

Can some share us the Supply and Demand zone indicators MQL5 file.....

[Sergey Golubev]

CodeBase

• Shved Supply and Demand - indicator for MetaTrader 4 
• NonLagDot - indicator for MetaTrader 5 ("Nonlagdot is the supply and demand indicator that calculates a possible trend considering market forces domination.")

The forum

• Supply and Demand Expert Advisor 
• more on search here

[Sergey Golubev]

Video - 

• Supply and Demand - simple explanation: #94
• Supply / Demand and Odds Enhancers - Part 1:#95 
• Supply / Demand and Odds Enhancers - Part 2: #96

[Udhaya Kumar]

Sergey Golubev:

CodeBase

• Shved Supply and Demand - indicator for MetaTrader 4 
• NonLagDot - indicator for MetaTrader 5 ("Nonlagdot is the supply and demand indicator that calculates a possible trend considering market forces domination.")

The forum

• Supply and Demand Expert Advisor 
• more on search here

Thank you so much bro......Do you one for MT5?? Shved S & D ??

[Sergey Golubev]

Udhaya Kumar:

Thank you so much bro......Do you one for MT5?? Shved S & D ??

 for MT4 only sorry.

[Sergey Golubev]

Sergey Golubev:

CodeBase

• Shved Supply and Demand - indicator for MetaTrader 4 
• NonLagDot - indicator for MetaTrader 5 ("Nonlagdot is the supply and demand indicator that calculates a possible trend considering market forces domination.")

The forum

• Supply and Demand Expert Advisor 
• more on search here

This indicator was converted to Metatrader 5 -

----------------

Shved Supply and Demand - indicator for MetaTrader 5

This is MQL5 version of Shved Supply and Demand written by Shved and upgraded by eevviill7 from this link.

[Sergey Golubev]

Forum on trading, automated trading systems and testing trading strategies

Supply & Demand

Sergey Golubev, 2026.01.31 06:15

From Novice to Expert: Statistical Validation of Supply and Demand Zones

The analysis of supply and demand zones represents a cornerstone of price action trading, rooted in the timeless economic principle of market imbalance. For the discretionary trader, these zones are identified through visual pattern recognition—a skill honed by experience. However, this reliance on subjective judgment creates a significant reproducibility challenge, forming the primary barrier to effective automation. While the theoretical logic of these zones is well-established, its translation into precise, computational rules remains elusive, often defaulting to arbitrary numerical thresholds.

[Sergey Golubev]

Interactive Supply and Demand Zone Manager in MQL5: From Manual to Automated Lifecycle

This system is built in MQL5 to be consumed by high-performance trading tools. It moves the burden of chart maintenance from the trader to the environment, allowing for a more focused and professional approach to live market execution.

[Sergey Golubev]

Interactive Supply and Demand Zone Manager in MQL5 (Part II): Event-Driven Architecture and Persistent Lifecycle Logging

In Part I of this series, we introduced a dynamic supply and demand zone management framework capable of transforming ordinary chart rectangles into actively managed market structures. Rather than treating support and resistance zones as passive visual annotations, we developed a system capable of creating, maintaining, merging, invalidating, and restoring structural regions as market conditions evolved.

[Sergey Golubev]

Interactive Supply and Demand Zone Manager in MQL5 (Part III): Zone Analysis, Stateful Interaction, and Pending Event Management

In Part I of this series, we introduced a dynamic supply-and-demand zone management framework that transforms static chart annotations into actively managed market structures. Rather than treating support and resistance as passive visual references, the system defines zones as lifecycle-aware entities. Zones support deterministic creation, modification, invalidation, restoration, and state transitions as market conditions evolve.

...

In Part II, this runtime framework was refactored into a structured event-driven architecture, where system execution was organized around discrete market responses rather than continuous tick-based polling. Alongside this shift, a dedicated logging subsystem was introduced to replace informal debug outputs with a persistent, append-only event record.