We are validating a local MT5 build 6258 DEMO installation and Python binding 5.0.6231. Execution remains disabled. Please provide a dated authoritative reference or identify the correct team for the following:
1. For MetaQuotes-Demo, what is the exact epoch/clock convention of XAUUSD and EURUSD MqlTick.time/time_msc and the corresponding Python symbol_info_tick values? A read-only native capture on 16 October 2026 found native server time 10800 seconds ahead of PC GMT, with both interfaces returning tick values in that server-time range. We have not subtracted an offset. Please reconcile this with the Python documentation's UTC convention.
2. What named timezone or fully specified transition rules govern the current server, including DST transition instants, historical applicability and planned changes? An observed offset alone is insufficient for our UTC mapping.
3. What are the applicable XAUUSD quote/trade sessions, maintenance breaks, holidays/early closes and daily rollover cutoff? Please clarify equal/zero session endpoints and boundary inclusivity. Our API snapshot is an observation, not a complete schedule.
4. What current public account-group/product reference identifies this USD hedging demo tariff? SymbolInfoCommissions returned zero rules without error for XAUUSD/EURUSD. Does that exclude all relevant entry/exit, minimum/maximum, tiered, daily/monthly or separate fees? Please state currency/conversion, posting timing and exact applicability; do not assume zero from our query.
5. Please confirm swap units, long/short rates, weekday/holiday multipliers and the exact liability cutoff independently of posting time. Observed XAUUSD values were points mode, -12.6 long/-4.6 short.
6. Are automated demo EAs and local read-only metadata/calendar exporters permitted? What terms cover internal storage/use of calendar data, completeness, revisions and latency? Is any breaking-news coverage or delivery commitment provided? Please distinguish platform testing from representative broker execution/fee validation.
We request documentation/clarification only: no new account, transaction, subscription, account change or increase of risk. We can supply a sanitized technical sample if needed after checking it for private information.
- MetaQuotes-Demo XAUUSD rollover time / server timezone / DST clarification
- Authoritative Python tick timestamp semantics for the MetaQuotes demo service
- MetaQuotes-Demo XAUUSD commission clarification SymbolInfoCommissions returns 0
Forum on trading, automated trading systems and testing trading strategies
MT5 Python API Timestamp Discrepancy on MetaQuotes-Demo — Build 6259
Sergey Golubev, 2026.10.14 09:02
It was already discussed many times, for example: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