OctaFX Demo vs Real: Mobile-First Transition And The APAC Behavioural Gap
By Joanne Cassar / 12. Oct 2026
read moreEvery MT4 or MT5 chart timestamps its candles using the broker's server time, not your local Bangladesh Standard Time (BDT, UTC+6) and not GMT. Most brokers run their servers on a GMT+2 or GMT+3 offset, sometimes shifting with European daylight saving, which means a typical broker's daily candle "midnight" does not line up with midnight in Dhaka. For a Bangladeshi trader, this creates a fixed, roughly 3-to-4-hour gap between when your broker's trading day rolls over and when your own local day rolls over, which matters directly for strategies built around daily or weekly candle opens, session breakouts, or economic-calendar timing.
This guide explains why brokers use the offsets they do, exactly how that interacts with BDT, and how to check and adjust for your specific broker.
MetaTrader 4 and MT5 platforms display three different clocks, and traders frequently confuse them:
Changing your device's time zone settings changes only how your own clock displays; it has no effect on how the broker's server timestamps historical or live price bars. The server time is fixed by the broker, and traders based anywhere in the world see the same underlying bar timestamps.
The forex market has no single central exchange and no official daily close, unlike a stock exchange. By long-standing market convention, the forex trading day is treated as running from the New York close (5:00 PM Eastern Time) to the next New York close, which keeps a standard trading week at exactly five daily candles, Monday through Friday, without an artificial extra "Sunday candle" caused by the market's Sunday evening reopening.
To align a broker's midnight server time with the 5:00 PM New York close, the server needs to sit at an offset of New York time plus 7 hours, commonly written as "NY+7." Because New York observes its own daylight saving schedule, a server that only shifts between GMT+2 (winter) and GMT+3 (summer), commonly Eastern European Time (EET), comes close to matching NY+7 for most of the year, which is why the overwhelming majority of MT4 and MT5 brokers, regardless of where they are legally based, run their trade servers on this GMT+2/GMT+3 pattern rather than on a country-specific local time. Some brokers use GMT+0 or GMT+1 instead, which produces a visibly different daily bar structure, including a short one-to-two-hour Sunday bar, depending on the specific offset and the current US daylight-saving state.
Bangladesh Standard Time (BDT) is a fixed UTC+6 year-round, since Bangladesh does not observe daylight saving. A typical GMT+2/GMT+3 broker server therefore sits 3 to 4 hours behind Dhaka time, depending on the time of year and on whether the broker's own offset shifts with European daylight saving.
|
Broker Server Offset |
Approximate Gap to BDT (UTC+6) |
|
GMT+2 (European winter) |
Server is 4 hours behind Dhaka |
|
GMT+3 (European summer) |
Server is 3 hours behind Dhaka |
|
GMT+0 |
Server is 6 hours behind Dhaka |
|
NY+7 (rare among retail brokers) |
Server is close to, but not always exactly, aligned depending on US DST |
This means a broker's daily candle, which typically opens at server midnight, does not open at midnight in Dhaka. Depending on the specific offset, it commonly opens somewhere in the mid-morning to early afternoon in Bangladesh, not overnight.
If your strategy relies on the daily candle's open or close price, such as a daily pivot calculation, a "previous day's high/low" breakout, or a daily moving average, the candle you are reading closes at the broker's server midnight, not at midnight BDT. Two brokers with different server offsets will show slightly different daily candles for the same currency pair on the same calendar date, which can change your indicator readings and entry signals.
Because the trading week is built around the New York close convention, the weekly candle's open on a Monday is likewise tied to server time, not Dhaka time. If you trade weekly opening-range or gap strategies, confirm exactly when your broker's weekly candle opens in your own BDT clock, not just "Monday morning" in a general sense.
Many popular MT4/MT5 indicators mark the London or New York session using fixed server-time hour inputs. An indicator built for a GMT+2 server will mark the wrong hours if your actual broker runs GMT+0 or GMT+3, and will certainly need adjusting relative to your own BDT-based mental model of "evening London session."
Most in-platform economic calendars display event times in server time by default. A release listed for "14:30" on your platform may correspond to a different clock time in Dhaka depending on your broker's offset, so always cross-check against a calendar you have explicitly set to your own local time zone or GMT.
Overnight swap charges are calculated at server midnight, not at midnight BDT. Positions held across that specific server-time boundary incur the swap, which again shifts relative to your own local clock depending on the broker's offset.
Assume your broker's server currently shows GMT+3 (a common summer setting). To convert any server-time reading to BDT:
BDT time = Server time + 3 hours
So if your platform shows a daily candle opening at server time 00:00, that corresponds to 3:00 AM BDT. If the same broker later shifts to GMT+2 for the European winter period, the same server midnight would then correspond to 4:00 AM BDT. Because Bangladesh itself never changes its clocks, this 1-hour shift in the gap happens twice a year, driven entirely by the broker's own daylight-saving pattern, not by anything changing locally in Bangladesh.
Using an illustrative GMT+3 server as a reference point:
|
Session |
Approximate BDT Time |
|
Sydney/Tokyo open |
Around 5:00 AM – 6:00 AM |
|
London open |
Around 1:00 PM |
|
New York open |
Around 6:00 PM |
|
London/New York overlap |
Around 6:00 PM – 9:00 PM |
|
Broker's daily candle "midnight" (server time) |
Around 3:00 AM |
Always verify these figures against your own specific broker's confirmed offset, since the exact hour shifts depending on which server time your broker uses and the current daylight-saving state in Europe and the US.
Rather than re-deriving the offset every time you open your platform, build a small reference sheet once and keep it next to your trading setup:
This small amount of upfront work removes a recurring source of confusion that affects many traders in fixed, non-DST-observing time zones like Bangladesh, not just beginners.
If you are comparing two or more brokers and server-time alignment genuinely matters to your strategy, ask each one directly:
A broker willing to answer these clearly and specifically is generally more transparent about its infrastructure overall, which can be a useful secondary signal alongside your evaluation of spreads, execution, and regulation.
If you run an Expert Advisor, whether one you built yourself or a commercial product, and it includes any time-based logic, such as avoiding trades near rollover, restricting activity to specific sessions, or closing positions before the weekend, check carefully how that logic reads time. Most EAs use TimeCurrent() in MQL4/MQL5, which returns server time, not GMT and not your local BDT clock. An EA built and tested by its author on a GMT+2 broker may behave differently on your GMT+3 or GMT+0 broker unless its time-based rules are written to detect and adjust for the actual server offset automatically. Before running any EA live, test it on a demo account with your actual broker for at least a few days specifically around the weekend and rollover period, to confirm its time-based behavior matches what you expect from Dhaka.
Most MT4 and MT5 brokers use a GMT+2 (winter) or GMT+3 (summer) server offset, aligned with Eastern European Time, because this closely approximates the New York-close-based convention that keeps the trading week at exactly five daily candles.
Broker server time is set to align with the global market convention around the New York close, not with any individual trader's local time zone. A server using Bangladesh's UTC+6 offset would not align daily candles with the standard NY-close convention most traders and indicators expect.
Commonly 3 to 4 hours, depending on whether the broker's server is currently on GMT+2 or GMT+3, since Bangladesh Standard Time is a fixed UTC+6 with no daylight saving of its own.
Yes. Overnight swap is calculated at the broker's server midnight, not at midnight in Bangladesh, so the specific BDT clock time at which your swap is charged shifts depending on your broker's current offset.
Compare the time shown in your MT4 or MT5 terminal against GMT/UTC from a reliable source, or ask your broker's support team directly for the current offset and its daylight-saving policy.
The in-platform calendar typically displays event times in server time by default. Cross-check against a calendar explicitly set to GMT or your own local time zone to avoid confusion.
Broker server time is not a minor technical footnote for Bangladeshi traders; it directly affects daily and weekly candle readings, session indicator accuracy, swap timing, and economic calendar interpretation, because Bangladesh's fixed UTC+6 clock sits several hours ahead of the GMT+2/GMT+3 offset most brokers actually use. Confirm your specific broker's current server offset directly, recheck it after each European or US daylight-saving change, and adjust any indicator or strategy that assumes server time equals your own local BDT clock.
Forex trading involves substantial risk and may result in the loss of your invested capital. This article is for educational and informational purposes only and does not constitute financial, investment, or trading advice. Broker server time conventions, daylight-saving schedules, and platform behavior may vary and can change. Always verify your specific broker's current server time and offset directly before relying on it for time-sensitive strategies.