Check this thread please - Can MQL5 uniquely determine the UTC open time of historical CopyRates bars?
Can MQL5 uniquely determine the UTC open time of historical CopyRates bars?
- 2026.10.09
- www.mql5.com
Subject: Can MQL5 uniquely determine the UTC open time of historical CopyRates bars...
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Please confirm the timestamp convention for EURUSD on MetaQuotes-Demo / MetaQuotes Ltd., using MT5 terminal build 6258 and the official Python MetaTrader5 package 5.0.6231.
At computer observation 2026-10-12 21:53:57.718959 UTC, symbol_info_tick returned time=1791852836 and time_msc=1791852836332. Interpreting that integer directly as Unix UTC puts it approximately 10,798.613 seconds ahead. A following observation similarly led by about three hours. Nearby public-time measurements indicated the computer was only approximately 2.53 seconds behind their references.
An earlier native MQL5 diagnostic on build 6256 also observed about three hours between tick time and computer-derived TimeGMT, with matching latest M15/H1 candle epochs in a nearby Python capture. We have not applied a correction.
Could you confirm:
1. Are Python tick/bar time fields true UTC epoch values, or epoch-encoded server wall-clock values on this server? Does the convention differ between quote and history APIs?
2. What server UTC offsets and daylight-saving transition rules apply, with effective dates for the available historical data? Were there any changes during 2025–2026?
3. Is this an expected server convention or a known terminal/Python issue, and is there a supported documented conversion or fix?
Please provide an official reference or dated server-specific confirmation. We need to preserve original values and document any conversion before research imports can pass.