MetaQuotes-Demo EURUSD: provider confirmation of 2026 historical UTC/DST mapping (build 6286, Python 5.0.6231)

[Nyasha Mandizvidza]

Please route this question to the MetaQuotes-Demo market-history/time-semantics owner. We need a provider-confirmed mapping for EURUSD, UTC calendar year 2026, using MetaTrader 5 terminal build 6286, Python MetaTrader5 5.0.6231, Windows cpython-314, and the native Python terminal connection.

The relevant read-only interfaces are symbol_info_tick(), copy_ticks_range() and copy_rates_range() with M1 bars. Please confirm:

1. What event the returned tick time/time_msc and M1 opening time represent, their epoch/units, and whether they encode UTC or server-local clock labels.

2. How UTC-aware Python datetimes, equivalent +02-aware datetimes and integer seconds are interpreted as historical query bounds, including endpoint rules.

3. The exact UTC-effective offset intervals for 2026, including both DST transition instants, which DST calendar applies, and ambiguous/repeated or missing local-label handling.

4. Whether the rule applies to historical EURUSD data retrieved by this runtime, including known per-symbol exceptions, migrations, relabeling or revisions.

5. A versioned specification or attributable engineering statement with its applicability dates. Please identify any behavior that is not guaranteed.

We retain original raw labels and input/output captures. A 2016 public EET statement supports our research hypothesis, but cannot independently identify the exact 2026 historical transition behavior. Current authenticated UTC observation bounds and exact subsequent history matches also do not measure past source-event age or establish a complete historical schedule.

This request concerns data semantics only. It requires no password, account access, order placement or execution permission.

[Sergey Golubev]

Look at the post #1