STRASMORE/EXPLORE 3,094 QUERIES

US session boundaries in New York, UTC and Israel time

Answered against 22 years of US equities and 12 years of US options data and published with the query that produced it. This result is stored as of 2026-10-05, from US Premarket and After-Hours in Israel Time.

as of series 4×7read in context →
US session boundaries in New York, UTC and Israel time — 4 rows by 7 columns, computed from US exchange, SIP and OPRA data.
us_session_boundarynew_york_clockutc_clockisrael_clockisrael_calendar_daynew_york_utc_offset_hoursisrael_utc_offset_hours
Premarket session opens04:0008:0011:00same day-43
Regular session opens09:3013:3016:30same day-43
Regular session closes16:0020:0023:00same day-43
After-hours session ends20:0000:0003:00next day-43
Rows × columns
4 × 7
Computed
Completeness
No missing values
Source
US exchange, SIP and OPRA market data
Licence
Strasmore terms · free, no signup
Formats
JSON · CSV · the SQL below

What each column holds

Column definitions for US session boundaries in New York, UTC and Israel time, derived from the stored result.
ColumnTypeRangeNotes
us_session_boundary text 4 distinct values
new_york_clock text 4 distinct values (04:00, 09:30, 16:00…)
utc_clock text 4 distinct values (00:00, 08:00, 13:30…)
israel_clock text 4 distinct values (03:00, 11:00, 16:30…)
israel_calendar_day text 2 distinct values (next day, same day)
new_york_utc_offset_hours number every row is -4
israel_utc_offset_hours number every row is 3

Computed from Strasmore's warehouse of US exchange, SIP and OPRA market data. Equity prices are delayed; options greeks and implied volatility are end-of-day. This result is stored, not recomputed on load — it is exactly the numbers that were returned on , and the query below is what returned them.

Run it yourself

This is the exact query behind the result above. Change a ticker, a date or a column and run it against the warehouse — no account, no key. The no-signup tier is smaller than the one this page was computed on; a query that reaches past it comes back saying which plan runs it.

SELECT
    tupleElement(b, 1)                                              AS us_session_boundary,
    tupleElement(b, 2)                                              AS new_york_clock,
    formatDateTime(toTimeZone(stamp, 'UTC'), '%H:%i')               AS utc_clock,
    formatDateTime(toTimeZone(stamp, 'Asia/Jerusalem'), '%H:%i')    AS israel_clock,
    if(toDate(toTimeZone(stamp, 'Asia/Jerusalem')) > toDate(toTimeZone(stamp, 'America/New_York')),
       'next day', 'same day')                                      AS israel_calendar_day,
    toInt32(timeZoneOffset(toTimeZone(stamp, 'America/New_York')) / 3600) AS new_york_utc_offset_hours,
    toInt32(timeZoneOffset(toTimeZone(stamp, 'Asia/Jerusalem')) / 3600)   AS israel_utc_offset_hours
FROM
(
    SELECT
        b,
        toDateTime(concat(toString(today()), ' ', tupleElement(b, 2), ':00'), 'America/New_York') AS stamp
    FROM
    (
        SELECT arrayJoin([
            ('Premarket session opens',  '04:00'),
            ('Regular session opens',    '09:30'),
            ('Regular session closes',   '16:00'),
            ('After-hours session ends', '20:00')
        ]) AS b
    )
)
ORDER BY new_york_clock
⌘/Ctrl + Enter

Work with this data in your AI assistant

Opens ready to query, with this page's data. Free, no account.

More from this analysisUS Premarket and After-Hours in Israel Time
UTC offsets and the Israel to New York gap, one Wednesday per week ahead series 57×5 → Upcoming windows where Israel is not seven hours ahead of New York series 3×7 → AAPL quoted spread and top-of-book size by hour, 16 September 2026 ranking 16×4 → This week's US sessions mapped onto Israeli weekdays and clock times table 5×5 → SPY volume by New York hour, with the London clock beside it series 16×4 → AAPL median quoted spread by hour across one full extended day series 16×4 → See all 3,094 queries →