A saved image of trading sessions can let you down by exactly one hour, and do it with complete confidence. London, New York and Sydney change their clocks on different calendars, and a platform accepts trades on its own schedule. Let’s go through Forex trading session times in UTC, show the conversion for different regions and put together a working observation window on intrade.bar. Here the clock helps you organize your analysis; it doesn’t promise profit on a schedule.
What a trading session is
The currency market has no single building where a bell rings in the morning and all the quotes switch on. Participants work in different financial centers, and activity moves along with their working day. The names “Asian,” “London” and “American” session help describe these periods.
That is why two tables can disagree even within the same time zone. One author took the start of the banks’ working day, another used a wider window, a third combined several centers. Before arguing about the right time, compare the underlying definitions. A label like “Forex time” without a date and explanation is too broad for a precise schedule.
The availability of a trading product is a separate matter. A changing schedule doesn’t guarantee that any digital option on that asset can be opened right now. A platform may have breaks, duration restrictions and payout conditions. For intrade.bar, the financial centers’ calendar is context for observation; the available pair and trade parameters are checked directly in the terminal.
One clear model for the conversion
In this article we use a sample window of 08:00–17:00 local time in each center. It doesn’t claim to be a universal schedule for all of Forex. Its job is to provide the same starting convention so you can check the conversion to UTC and then to your own local time.
If your calendar marks the Tokyo or Sydney session differently, plug in its local boundaries and do the same conversion. You can’t carry the hours from the table directly over to the schedule of intrade.bar, exchange-traded futures or an individual bank. A shared city name doesn’t make these regimes the same.
UTC doesn’t switch to daylight saving time. What changes is how local clocks relate to it: London is on GMT or BST, New York on EST or EDT, Sydney on AEST or AEDT. A label saying “New York, UTC−5” is correct for one regime, but not for the whole year. In a calendar it is better to store the time zone name, not just today’s offset.
Session table in UTC: January and July 2026
Below, the chosen 08:00–17:00 window is converted for an ordinary weekday in two months. The note “prev. day” means the previous calendar date in UTC. For example, Monday morning in Sydney begins on Sunday evening on the common timeline.
| Center | Local window in the model | January 2026 in UTC | July 2026 in UTC |
|---|---|---|---|
| Sydney | 08:00–17:00 | 21:00 prev. day – 06:00 | 22:00 prev. day – 07:00 |
| Tokyo | 08:00–17:00 | 23:00 prev. day – 08:00 | 23:00 prev. day – 08:00 |
| London | 08:00–17:00 | 08:00–17:00 | 07:00–16:00 |
| New York | 08:00–17:00 | 13:00–22:00 | 12:00–21:00 |
In January Sydney uses UTC+11, and in July UTC+10. For London the corresponding values are UTC+0 and UTC+1, for New York UTC−5 and UTC−4. Tokyo stays at UTC+9. These offsets produce the hours in the table: you apply the offset with the opposite sign to the local time.
Months are more precise here than the words “winter” and “summer.” In January it is winter in the UK and summer in Australia. For an international audience, a seasonal label without a city creates needless ambiguity. The date, the local window and UTC make the table equally clear to a reader in Latin America, Asia or Africa.
Why transition weeks are different
In 2026, New York switched to daylight saving time on March 8 and London on March 29. The switches back took place on October 25 in London and November 1 in New York. Between these dates, the usual local time difference between the two cities temporarily changed. An image that is correct for January is no longer enough for such a week.
In our model, the London and New York windows overlap from 13:00 to 17:00 UTC in January and from 12:00 to 16:00 UTC in July. On weekdays from March 9–27 and October 26–30, 2026, the overlap is 12:00–17:00 UTC: London is on GMT while New York is on EDT.
Sydney has its own calendar: in New South Wales, daylight saving time in 2026 ended on April 5 and began on October 4. Don’t apply these dates to all of Australia: the rules differ between states. For the next year, update the dates separately, even if the usual hours for most months stay the same.
How to convert UTC to your own time
Add your current local offset and check the calendar date. An event at 22:00 UTC happens at 02:00 the next day in a UTC+4 zone. A date error is nastier than it looks: your journal may show a trade “tomorrow” while the exported file still assigns it to the previous day.
For a reader in UTC+7, the London window of our model corresponds to 15:00–00:00 in January and 14:00–23:00 in July. Your home clock may never change, but the British switch will still move the observation time relative to your evening. That is how another region’s seasonal schedule finds its way into your daily routine.
Likewise, a fixed home zone of UTC−5 matches New York time in January, but not in July, when New York uses UTC−4. So it is better to save the event in your calendar as Europe/London or America/New_York and check how it displays on the chosen date. These identifiers account for seasonal rules, unlike a fixed number of hours.
Session overlaps are context, not a Call or Put signal
Simultaneous activity in several centers may come with a different character of movement than quieter hours. But you can’t derive the direction of the next candle from the London–New York overlap. Trends, ranges, reversals and sharp reactions to news all occur in the same window.
High activity doesn’t automatically mean a convenient entry. Price may move faster, cross a zone and come back before you have finished checking the parameters. For a digital option, what matters is where the price is at the specific moment of settlement, not the range over the whole hour. The biggest move of the day isn’t bound to give the best result for your chosen expiry.
If time is part of your strategy, test it as a separate condition. First decide whether you are comparing a fixed UTC hour or the same part of London’s local working day. These are different questions. You can’t merge them under one label like “European open” and expect the statistics to correct an imprecise definition on their own.
Putting together an observation window on intrade.bar
Imagine a practice demo session in November 2026 from 14:00 to 15:00 UTC. It falls within the overlap of the chosen London and New York windows. For Colombia that is 09:00–10:00, for the UAE 18:00–19:00, for Jakarta and Vietnam 21:00–22:00. This is an example of organizing your time, not a declaration of the best hour to trade.
Choose one available currency pair and one hypothesis you have already described, for example a reaction at a zone marked in advance. Open the TradingView chart on intrade.bar, check the time setting and the events calendar. Before a qualifying signal, check the asset’s availability, the required duration and the percentage shown. If any parameter doesn’t match the plan, record a skip instead of picking a random substitute.
If the trade you are studying lasts ten minutes and all results must be known by 15:00, the last acceptable entry is no later than 14:50 UTC. It is a simple but useful line in a trading plan. intrade.bar has no early closing: ending your session on schedule and cancelling an unfinished contract are different actions.
After the session, export closed trades to CSV and keep the times in UTC. In a separate column you can add the local window, the hypothesis version and the reasons for skips. intrade.bar statistics help compare assets and expiries, and grouping by chosen hours and additional conditions is easy to do separately. Don’t promise yourself a conclusion after one good session: collect comparable observations first.
News, holidays and breaks are checked separately
An economic calendar may show device time, UTC or a manually chosen zone. Before an event, check the setting, the date and the name of the release. A screenshot saved in another month is no substitute for the current entry. It is especially easy to make a mistake in the weeks when countries change their clocks at different times.
A holiday in one center doesn’t necessarily close the whole currency market. It may change who is participating and the character of activity while other centers keep working. The schedule of bank transfers, the availability of quotes and the ability to open a digital contract need not coincide either. Phrase the question specifically: which asset, which product and which moment are you interested in?
If the platform doesn’t offer the expiry you need or an asset is temporarily unavailable, a general session table doesn’t lift that restriction. Don’t move a trade to another instrument just to keep the planned number of trades. In that case you can end the session or keep watching without opening a trade, recording the reason for the skip for your review.
Bitcoin and daily limits run on their own clocks
On intrade.bar, BTC/USDT is available around the clock, including weekends; on weekends it is the only asset available. Its quotes come from Binance. This doesn’t mean currency pairs get the same schedule, or that a crypto session becomes a continuation of the London one. Bitcoin has a different market regime that requires its own hypothesis testing.
Duration is also checked separately: for BTC in Sprint, the minimum expiry is five minutes. Around-the-clock availability is not the same as being able to choose any expiry. Before a trade, what matters is the actual conditions in the trade form, including the percentage. The convenience of a single terminal doesn’t erase the differences between assets.
Another separate calendar is intrade.bar’s voluntary risk management. The day for limits starts at 00:00 Moscow time (MSK), or 21:00 UTC. This is the boundary for the settings, not the end of the London or New York session. If you have turned on limits, factor this moment into your plan; a limit you have set can only be changed the next day.
Start with one clear observation window on the intrade.bar demo and save it together with the date and UTC. After a clock change, recheck how it maps to your local time, and compare results using the same session definition. Then the schedule becomes a useful tool for organizing your trading, not just another picture you have to take on faith.
Questions and answers
Why do different Forex tables show different hours?
Authors may choose different local session boundaries, time zones or seasonal regimes. Here, a sample 08:00–17:00 window in each center is used for comparison; it is not the schedule of all market participants or of intrade.bar.
Which assets are available on intrade.bar on weekends?
On weekends BTC/USDT is available, with Binance as its source. Currency pairs don’t switch to a round-the-clock weekly schedule along with Bitcoin. Check the available duration and percentage in the terminal.
What time should I use to compare trades from the intrade.bar CSV?
The export uses UTC. Keep the original time and add the local session in a separate column, taking the date and seasonal offset into account. That way a clock change won’t mix up different working windows.
Place your first practice trade
A demo account opens right after registration
