Market Hours on MT4 and MT5 in Canada

On FxPro MT4 and MT5, all market hours are controlled by the trading server and by the settings of each symbol. The time shown in the platform is server time, not Canadian local time, so every candle, tick and order timestamp follows that same clock. Forex pairs usually trade almost continuously from late Sunday to late Friday in server time. CFDs on stocks, indices and commodities follow the hours of their underlying exchanges, sometimes with pre-market and post-market sessions when liquidity is available.

Since server time cannot be changed inside MT4 or MT5, a Canadian trader needs to translate server time into local time (Eastern, Central, Mountain or Pacific) when planning trades. The exact sessions for each instrument are visible in the Specification window in Market Watch and may be adjusted around daylight saving or schedule changes. Platform integration features such as Expert Advisors, custom indicators and the MT5 Python package all work with this same server-time framework. Any script or EA that filters trades by time, or any external tool that reads MT4/MT5 data, must use server timestamps and convert them if local Canadian time is required.

1. Open MT4 or MT5 and check server time in Market Watch
2. Right-click a symbol, open Specification and read trading hours
3. Note the offset between server time and local Canadian time
4. Configure indicators/EAs with the correct server-time windows
5. Test the setup on demo and then apply it on a live account

Trading servers typically run on a fixed GMT-based time so that the daily candle close aligns with the New York 17:00 Eastern Time close. That time zone does not automatically match the trader's location in Canada.

The offset between server time and Canadian time changes when Canada switches to or from daylight saving if the server clock itself stays constant. For example, the difference between Toronto and the server can move by one hour between winter and summer.

Useful ways to handle this in MT4/MT5:

• Use custom indicators that display both server time and local time on the chart
• Use EAs that convert server time internally and open trades only in defined windows
• Keep a small reference table or world clock showing server time vs local time

Every order, position history entry and bar in MT4/MT5 is stamped with server time, so any backtesting, manual log or external analysis needs to work from that base.

Each symbol in MT4 and MT5 has its own hours. These sessions define when quotes appear and when trading is possible. To check them:

• In Market Watch, right-click the symbol
• Select Specification
• Find the Sessions or Trading Hours field

Times there are listed in server time and can show one continuous block or several segments (for example, pre-market and regular hours). Sessions can also include short daily breaks, such as a rollover pause in forex.

Typical configurations include:

A trader can use this information to:

• Avoid trying to place orders when the symbol is closed
• Focus on hours with tighter spreads and better liquidity
• Set EA filters that respect the exact open and close times in server time

If a symbol seems unavailable at an expected time, checking Specification first usually clarifies whether the market is actually closed according to configured hours.

When a CFD on a stock or index includes extended hours, price updates appear during those periods and orders can be placed. Liquidity before and after the main session often differs from regular hours: spreads tend to be wider and volumes smaller, which can increase slippage and affect fill quality.

Chart structure also changes with extended hours. A daily candle on MT4/MT5 will include the full configured range, not just the main cash session. As a result, highs, lows or closes may differ from charts that show only regular exchange hours from other data providers.

Indicators that depend on session boundaries - such as daily pivot points, session-based volume profiles or statistics for a specific open or close - will calculate based on the entire trading window defined for that symbol. Traders who focus on particular sessions such as the New York cash open or the London close may need custom markers or indicators that highlight those times on the server-time chart.

MetaTrader integration options available on FxPro MT4 and MT5 can be used to build time-aware strategies around these market hours:

• Expert Advisors (EAs) in MQL4/MQL5 can include time filters so trades only open during defined server-time intervals, such as the London-New York overlap or a main North American session.
• Custom indicators can shade specific periods on the chart or label session opens and closes, helping visually map server time to the desired trading windows.
• Scripts can run one-off tasks like exporting data from a given date and time range.
• Price history can be exported from the terminal to CSV and then analyzed in spreadsheets, Python or other tools, always using server-time timestamps.
• MT5 supports an official Python package that connects to a local MT5 terminal to send orders and read data. All timestamps from this API are server based, so code should convert them to a Canadian time zone only if needed for display or logging.

Any automated approach that depends on market hours - such as avoiding low-liquidity times or focusing on overlaps - must treat server time as the reference and apply the correct offset.

Canadian traders work across several time zones, so a consistent mapping from server time to local time is essential. A simple approach is:

• Note the server time from Market Watch
• Compare it with the local computer clock
• Record the difference for standard time and for daylight saving time

Testing on a demo account helps confirm this understanding. A trader can place test orders around expected opens and closes, then review in the account history exactly when positions were opened and closed in server time.

Market hours and symbol sessions are occasionally adjusted, for example around major holidays or when underlying exchanges change schedules. Updates are typically communicated through client portals or platform messages, so checking for changes before significant events or public holidays reduces the chance of scheduling errors.