Clarification of MT5 Python symbol_info_tick() Timestamp Semantics
I am validating quote timestamps for a read-only analytics application using the MetaTrader 5 Python integration
I suspect that some AI engines must be generating a self-reinforcing loop for users. This topic has been repeating, almost word-for-word:
Forum on trading, automated trading systems and testing trading strategies
MetaTrader5 Python API timestamp semantics: UTC or broker server time?
Sergey Golubev, 2026.09.30 08:50
It was already discussed many times, for example:
I suspect that some AI engines must be generating a self-reinforcing loop for users. This topic has been repeating, almost word-for-word:
Most probably any AI Agent will generated similar message as long as the documentation is not fixed.
Except maybe the ones using new models which will have read the recent forum topics and answers that clarify the documentation.
Most probably any AI Agent will generated similar message as long as the documentation is not fixed.
Except maybe the ones using new models which will have read the recent forum topics and answers that clarify the documentation.
Thank you for clarifying. I never would've known that on my own. My only foray into AI use is with MQL5 Lite, MCP enabled, All requests enabled, Python integrated, and in "Dangerous" mode. It can grab anything and everything from mql5.com and elsewhere (all in Beta/demo, of course). More specifically, it has hit the Forum while using it.
Anyway, I really do hope that the documentation gets fixed. Not really for the sake of AI, but the sake of, well... reliable documentation.
time is Unix seconds (UTC), time_msc is milliseconds (UTC). Both refer to the same tick event from the broker. In practice time == time_msc // 1000 holds for broker-provided quotes, but I would not rely on it as a guarantee — if they disagree, prefer time_msc for higher precision and log the discrepancy. For analytics, treat the timestamp as the broker's server time at quote arrival, not as a synchronized clock; broker clocks can drift by seconds from your local clock. The MetaTrader 5 Python documentation under 'symbol_info_tick' covers the field definitions. For version-specific guarantees, the changelog (release notes) for build 6272 is the authoritative source.
Thank you for the replies so far.
Could anyone point me to an official MetaQuotes technical clarification or documentation specifically covering the Python symbol_info_tick() function for terminal version 5.0.0.6272 and Python package 5.0.6231?
In particular, I need to establish the clock basis of time and time_msc, whether their agreement is guaranteed, and how discrepancies should be handled. I understand that community experience may be useful, but I am looking for an official reference or an explicit confirmation of which guarantees are undocumented.
This is important for validating quote freshness in a read-only analytics application.
Thank you.
Could anyone point me to an official MetaQuotes technical clarification or documentation specifically covering the Python symbol_info_tick() function...
Based on the documentation, Python symbol_info_tick() is an analog of MQL5 SymbolInfoTick():
The information is returned as a tuple with the same fields as in the MqlTick structure. The function is an analog of SymbolInfoTick.
None is returned if an error occurs.
- www.mql5.com
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hello MetaQuotes community,
I am validating quote timestamps for a read-only analytics application using the MetaTrader 5 Python integration.
Environment
MT5 terminal build: 5.0.0.6272
Python MetaTrader5 package: 5.0.6231
Symbol: EURUSD
Could you please point me to official documentation or technical references covering these questions?
What are the units and precision of time and time_msc returned by mt5.symbol_info_tick()?
Is UTC explicitly guaranteed as the clock basis for these current-quote fields?
Are both fields guaranteed to refer to the same price-update event?
Is time == time_msc // 1000 guaranteed for broker-provided current quotes? What should an application do if the fields disagree?
Are there documented guarantees about timestamp accuracy, clock synchronization, update delays, unchanged prices, or disconnect/reconnect behavior?
Do the applicable guarantees cover terminal build 5.0.0.6272 and Python package 5.0.6231?
For each answer, please provide the official documentation URL, relevant section, and applicable versions where available. If a behavior is undocumented, please clarify that limitation.
This is for a read-only validation process. I am not requesting account access or trading assistance.
Thank you.