Server time, sessions and economic calendars

The essentials

Platform time may be server time rather than your location's time. Symbol sessions, maintenance and holidays determine trading availability. A calendar event does not require execution at a pre-announcement price.

Understand the mechanism, not just the definition

Candles, history and rollover may use server time while calendars and your clock use other timezones. Conversion must account for seasonal changes. An offset can compare different moments or assign a trade to the wrong date. Keep original timestamps alongside their conversion.

Example and verification

Record local time, server time and reference zone. Check seasonal changes before comparing different days. Read the instrument's session rather than a generic five-day forex description.

Worked case, step by step

A hypothetical UTC+3 server is eight hours ahead of UTC−5. Tuesday 01:30 server time corresponds to Monday 17:30 at UTC−5. If the server changes to UTC+2, the offset changes. Record the timezone applicable to the date rather than copying a seasonal rule.

What to verify when applying this

Synchronize time references when comparing spreads or incidents. Price and news alerts are notifications rather than orders; delivery can depend on connectivity and device settings.

Practice: verify it in your environment

Learn by observing the process and keeping its data. Complete this practice in demo or using documentation, without sending real orders or adding capital for the exercise. Record differences between the example and your account specifications.

1. Convert three history timestamps to one timezone and check the date.
2. Check market sessions, announcement calendar and rollover cutoff separately.

Test your understanding

Try the question before revealing the answer. Justify the conclusion and its assumptions rather than memorizing a number.