Official MetaTrader5 Python timestamp convention:  symbol_info_tick().time  /  time_msc

New comment
 
Hello MetaQuotes / MQL5 Technical Support,
I need an authoritative clarification about timestamp semantics in the official MetaTrader5 Python package. This is a read-only diagnostic; no orders are being placed.
Environment:
• MetaTrader5 Python package: 5.0.6180
• MetaTrader 5 terminal build: 6182
• Windows system clock: synchronized
• Local Windows timezone: UTC+03:00 Nairobi
• Symbol: EURUSD
On an MT5 demo terminal, symbol_info_tick().time and symbol_info_tick().time_msc are internally consistent, but when interpreted as Unix UTC epoch values, they appear approximately 10,800 seconds (three hours) ahead of the synchronized Windows UTC clock.
Example:
• MT5 tick time : 1790369298
• MT5 tick time_msc : 1790369298165
• Interpreted as UTC: 2026-09-25T20:48:18.165Z
• Windows UTC at capture: approximately 2026-09-25T17:48:18Z
Please confirm the documented meaning of these returned timestamp fields:
1. Are symbol_info_tick().time and time_msc UTC Unix epoch values, broker trade-server-local epoch values, terminal-local values, or another time basis?
2. Do copy_ticks_from() and copy_ticks_range() use the same timestamp convention?
3. What time basis should be used for the Python datetime request bounds passed to copy_ticks_from() and copy_ticks_range() ?
4. If the fields are server-time values, how can a client obtain the official server-time-to-UTC conversion and DST schedule?
5. Does this behavior depend on broker, server, terminal build, or Python package version?
The Python documentation says terminal data uses UTC, but this observed result appears to match a broker UTC+3 server clock. Please clarify the authoritative behavior for the Python integration.
I am not seeking trading, EA, or strategy support—only the documented timestamp convention for the API.
Thank you.
 
Ezeckiah Mwaisanila:
Hello MetaQuotes / MQL5 Technical Support,
I need an authoritative clarification about timestamp semantics in the official MetaTrader5 Python package. This is a read-only diagnostic; no orders are being placed.
Environment:
• MetaTrader5 Python package: 5.0.6180
• MetaTrader 5 terminal build: 6182
• Windows system clock: synchronized
• Local Windows timezone: UTC+03:00 Nairobi
• Symbol: EURUSD
On an MT5 demo terminal, symbol_info_tick().time and symbol_info_tick().time_msc are internally consistent, but when interpreted as Unix UTC epoch values, they appear approximately 10,800 seconds (three hours) ahead of the synchronized Windows UTC clock.
Example:
• MT5 tick time : 1790369298
• MT5 tick time_msc : 1790369298165
• Interpreted as UTC: 2026-09-25T20:48:18.165Z
• Windows UTC at capture: approximately 2026-09-25T17:48:18Z
Please confirm the documented meaning of these returned timestamp fields:
1. Are symbol_info_tick().time and time_msc UTC Unix epoch values, broker trade-server-local epoch values, terminal-local values, or another time basis?
2. Do copy_ticks_from() and copy_ticks_range() use the same timestamp convention?
3. What time basis should be used for the Python datetime request bounds passed to copy_ticks_from() and copy_ticks_range() ?
4. If the fields are server-time values, how can a client obtain the official server-time-to-UTC conversion and DST schedule?
5. Does this behavior depend on broker, server, terminal build, or Python package version?
The Python documentation says terminal data uses UTC, but this observed result appears to match a broker UTC+3 server clock. Please clarify the authoritative behavior for the Python integration.
I am not seeking trading, EA, or strategy support—only the documented timestamp convention for the API.
Thank you.

Forum on trading, automated trading systems and testing trading strategies

MetaTrader5 Python history_orders_get/history_deals_get — authoritative time semantics

Alain Verleyen, 2026.09.25 15:05

The same applies to the whole API.

You need to use UTC timezone in your parameters, and the returned data are broker server time.


New comment