- Phone time, calendar time and platform time are three different clocks until you map them
- Server time drives swap, daily bars and many pending expiries
- US data is scheduled in US civil time; convert via UTC, not via a screenshot from last March
- DST in the US, EU and your home country can each shift the offset independently
- A one-hour error around NFP or rollover is an execution error, not 'bad luck'
Quick Answer#
Your phone uses local civil time. Your broker uses a server clock. An economic calendar is only useful if both of those clocks are mapped through UTC.
Swap cutoff, many daily candles, and pending-order expiry follow the server, not the time under your thumb.
Risk warning: Being one hour early or late into NFP, FOMC or rollover can mean trading the worst spread window of the day. This is operations, not a strategy edge. See the disclaimer.
1. Three Clocks, One Instant#
Short Answer
One market event has one UTC instant. Your phone, the calendar UI and MetaTrader may each label that instant differently.
Detailed Explanation
Retail traders mix three displays:
- Local time — what Android, iOS or Windows show.
- Calendar time — whatever timezone the website last stored in a cookie.
- Server time — the broker's trading server, visible in the platform.
NIST maintains civil time standards. Brokers do not have to use your capital city's DST rules. Many retail FX servers are documented by the broker as GMT, GMT+2 or GMT+3, sometimes switching in spring/autumn, sometimes not.
ForexTradeLab's economic calendar keeps event times in UTC in the page markup and converts them in the browser to your device timezone. That is the right architecture. It still cannot guess your broker's server offset unless you measure it.
Pair this article with how to read the economic calendar (which release matters) and forex market hours (which session has liquidity).
Example
US nonfarm payrolls are scheduled by the BLS in US Eastern Time. In winter that is UTC−5; after the US spring clock change it is UTC−4. A Riyadh trader (UTC+3, no DST) sees a one-hour local shift when the US changes clocks even though Saudi clocks did not move.
Common Mistake
Saving “NFP is 15:30” in a phone note forever. That number is a local label, not a law of nature.
Professional Tip
Journal the event as UTC first, then as server time. Local time is for whether you are awake, not for order logic.
2. How to Read MetaTrader Server Time#
Short Answer
Look at the platform clock, not the candle tooltip alone. Tooltips follow chart settings; the server clock is the trading reference.
Detailed Explanation
In MetaTrader, the time in the status bar (and on many Trade headers) is the server time used for that connection. Chart shift and period separators can hide the mismatch if you never look down.
Your job is to compute:
Server offset today = platform time − UTC
Do this on a quiet minute. News days distort nothing about the offset; they only punish you if the offset is wrong.
If you use a VPS, the VPS Windows clock can be yet another zone. Keep the VPS on UTC or local — but always read the terminal clock for trading.
Example
UTC is 12:00. The MT5 status bar shows 15:00. Server offset is UTC+3 that day. An event at 12:30 UTC prints at 15:30 server.
Common Mistake
Changing the Windows timezone to “match the broker” and then trusting Outlook, banking apps and calendar invites that now lie.
Professional Tip
Leave the OS on your real city. Put a tiny UTC clock widget on the desktop if you need a third reference.
3. News: Convert Official Times Through UTC#
Short Answer
Take the publisher's timezone (BLS Eastern, Fed as published), convert to UTC, then to server time. Never convert “from last month's screenshot.”
Detailed Explanation
FOMC calendars and BLS schedules are authoritative for when the US institution releases. They are not MetaTrader schedules.
Use:
- Official page → Eastern (or the zone they state).
- Convert to UTC (watch US DST).
- Add your measured server offset.
Then mark the economic calendar and decide whether you will be flat, reduced, or trading a second wave. Size with the news risk calculator.
Example
A statement due at 14:00 US Eastern in July (EDT, UTC−4) is 18:00 UTC. On a UTC+2 server that is 20:00 server. The same 14:00 Eastern in January (EST, UTC−5) is 19:00 UTC and 21:00 on that same UTC+2 server.
Common Mistake
Using a Telegram “NFP in 10 minutes” ping without checking whether the ping bot used IST, GMT or the broker's clock.
Professional Tip
For GCC traders: your local clock is often stable. US and EU clocks are not. The error shows up twice a year, always around the data you care about.
4. Swap Cutoff Is a Server Event#
Short Answer
Overnight financing posts when the position is still open at the broker's cutoff on server time. City folklore is not your contract.
Detailed Explanation
Spot FX has a market convention around New York 17:00 for value-date rollover. Your retail CFD/forex book may use a different cutoff on the server. Triple-swap weekdays (often Wednesday on many FX books) are also server-dated.
Read what is swap for the economics. This article is only the clock. If you close at 16:50 local thinking you beat rollover, but the server already passed cutoff, you still pay (or receive) swap.
Contract specification and the Members Area beat any blog's example hour.
Example
You plan to close before swap. Local time is 23:50. Server time is already 00:10 next calendar day. You are late.
Common Mistake
Assuming “no swap on Islamic” means cutoff time no longer matters. Swap-free books can still use admin fees or time-based charges. Verify terms.
Professional Tip
Once a quarter, screenshot specification swap values and write the cutoff you observed. Rates change; the clock habit should not.
5. Sessions, DST and “London Open” Labels#
Short Answer
Session names are liquidity stories. Their local clock labels move when either London or New York or you change DST.
Detailed Explanation
Best time to trade is about overlap and spread, not about a tattooed “08:00.” When Europe springs forward a week before the US, the London–New York overlap length in local hours changes.
Your broker server may:
- stay on GMT all year, or
- jump with a European DST rule, or
- follow another internal convention.
You cannot infer the rule from the brand name. Measure the offset, then re-measure after each DST weekend.
Example
A trader in Dubai (no DST) who learned “London open 11:00” in February will be one hour off after the UK clock change until they update the note.
Common Mistake
Using a session indicator that hard-codes hours without a DST toggle, then blaming the broker for “fake London.”
Professional Tip
Label sessions as UTC ranges in your playbook (for example, “London active ≈ 07:00–16:00 UTC in winter”). Convert once per season.
Checklist#
- Read the MetaTrader status-bar clock and write today's UTC offset.
- Convert official US/EU release times via UTC, not via memory.
- Recalculate after US DST, EU DST and any local DST.
- Treat swap cutoff as server time; confirm on your specification.
- Keep the computer on local time; do not hijack Windows to mimic the broker.
- Use the economic calendar with the timezone chip, then map that instant to the platform.
- Flat or reduce size if you cannot supervise the converted window.
Glossary#
- UTC: The reference timescale for conversion; not a trading session.
- Server time: The broker platform clock that timestamps deals and daily processes.
- Offset: Hours (and minutes) between UTC and server time today.
- DST: Daylight saving; the US, EU and some other regions change on different dates.
- Cutoff / rollover: Server instant when overnight financing is applied if the position is still open.
- Civil time: The clock your phone uses for ordinary life.
Related reading#
- Forex economic calendar
- How to read the economic calendar
- Market hours, liquidity and slippage
- What is swap
- Second-wave news trading
- Hedging vs netting in MetaTrader
Qualified next step: Align clocks on demo for one full week of data, including one high-impact US release. If you then open a live account (XM from a low minimum where available; optional code FXTRD), the first live skill is still time, not leverage. CFDs remain high risk; never deposit money you cannot afford to lose. Disclosure: ForexTradeLab may earn a commission from qualifying accounts.
Comments
Add a useful note for other traders. We review comments before publishing.