New York's 9:30 a.m. open maps to 9:30 p.m. in Beijing during daylight time and 10:30 p.m. during standard time. Whether to edit the strategy depends on its time-zone implementation.
It's 9:30 p.m. in Beijing, but your strategy's US market-open window has not started. After US daylight saving time ends, New York's 9:30 a.m. open falls at 10:30 p.m. in Beijing. Whether you need to edit the strategy depends on how its trading window is defined: a named regional time zone or a fixed UTC offset.
A trading bot can involve market-local time, a strategy time zone, a server time zone and the interpretation of incoming timestamps. America/New_York has date-dependent rules. When reviewing an AlgoRover strategy revision, check the actual running instance and whether its candle timestamp marks the start or end of the bar.
What happens to the US stock-market open in Beijing time?
Identify the market clock the rule followsCrypto trades around the clock, but a crypto strategy may still use the US stock-market open as a timing reference. Interpret that rule against the market it names, including the relevant trading calendar.
Should you add an hour to every time parameter?
Named time zones contain calendar rulesA region identifies rules that can change with the date. A fixed offset specifies a constant distance from UTC. Test the conversion on a specific date and compare it with the market-local target.

How do candle timestamps line up with the entry window?
Follow one timestamp through the whole decisionA correct-looking desktop clock cannot show how a strategy interpreted an incoming bar. Following one record from UTC to the window check reveals where the extra hour entered the calculation.
Ask AI for a before-and-after daylight-saving schedule
Keep the rule anchored to its intended marketWrite down which market clock the rule follows. A dated conversion then remains a reliable reference when you change servers or display time zones.
Trading time zones and daylight saving: common questions
Does every trading strategy need a one-hour change after daylight saving ends?
Check the target and implementation. A correctly implemented regional time zone converts by date. A rule anchored to a fixed local time follows that definition; a hard-coded offset needs review against its intended market time.
How do exchange, strategy and server time zones differ?
Exchange time describes the market-local clock. Strategy time controls time-based rules. Server time affects system displays and local-time functions. Convert the same record to UTC, then compare each interpretation.
Why are there no trades after the trading window opens?
The window permits evaluation. Entry conditions, warm-up, cooldown, positions and order status still affect execution. Check fresh data, then the signal, submission and fill records.
Why can backtest and live trigger times differ?
Compare date-specific time-zone conversion, candle start versus end timestamps, and bar-close evaluation. Then inspect live data arrival and order response times, plus the revision used by the live instance.
Read next
Checking the period and data interval in a backtest
What to verify between demo and live trading
Explore AlgoRover LiveSources
NIST: US daylight saving time
Investor.gov: regular US stock-market hours
QuantConnect: exchange, algorithm and data time zones
Next step
Test the strategy yourself
Use AlgoRover Research to check costs, drawdown, and performance across market periods before you keep testing.
Try AlgoRover Research Follow us on X Follow us on Reddit
Top comments (0)