MT5 Python API: Different Bid/Ask Prices for Identical Live and Historical Tick Timestamps

Hello MQL5 community and MetaQuotes developers,

I am investigating a reproducible difference between live and historical EURUSD tick data using the MetaTrader5 Python API 5.0.6231 on an ICMarketsSC-Demo Standard account.

On November 18, 2026, I captured three live ticks using symbol_info_tick() and compared them with historical data returned by copy_ticks_range() using COPY_TICKS_ALL.

The timestamps (time_msc) and flags matched exactly, but Bid and Ask were different.

Sample 1:
time_msc: 1795029458715
Live: Bid 1.09717 / Ask 1.09725
History: Bid 1.09721 / Ask 1.09721

Sample 2:
time_msc: 1795029461926
Live: Bid 1.09717 / Ask 1.09726
History: Bid 1.09721 / Ask 1.09722

Sample 3:
time_msc: 1795029466147
Live: Bid 1.09719 / Ask 1.09728
History: Bid 1.09723 / Ask 1.09724

In all three cases:

  • Historical Bid is 4 points higher.

  • Historical Ask is 4 points lower.

  • Historical spread is 8 points (0.8 pip) narrower.

  • The midpoint and flags remain identical.

The broker publishes a 0.8 pip markup for Standard accounts, but it is unclear whether this explains the difference between the two API calls.

I also observed that raw live tick timestamps were approximately 2 hours ahead of an independent UTC reference.

My questions are:

  1. Can symbol_info_tick() and copy_ticks_range() return different Bid/Ask values for the exact same time_msc?

  2. Does MT5 historical tick storage use a different pricing source or spread representation?

  3. Can historical ticks be updated after the initial query?

  4. Do the Python API tick timestamps represent actual UTC or broker server time?

I have checked the local Python code and found no Bid/Ask adjustment.

This is a read-only investigation. No trading orders were submitted.

Any technical explanation or documentation reference would be greatly appreciated.

Thank you.

Yes, they can differ. symbol_info_tick() gives the live quote stream with your account's markup added, while copy_ticks_range() reads the stored tick database, which keeps the raw feed. Your 4 points on each side is that markup. Timestamps are server time, not UTC.