★ TIME CONVERTER · TIME & DATE · BANGKOK
Indochina Time is UTC+7 year-round: Thailand observes NO daylight saving time, ever. At 12:00 ICT on October 24, 2026, it is 05:00 UTC the same day, 01:00 EDT on October 24 in the east, but already the previous evening in the west: 23:00 MDT on October 23 and 22:00 PDT on October 23. Enter any Bangkok date and time below: the converter subtracts 7 hours to reach UTC, then reads every US zone from that same moment.
The trap with Bangkok is the date, not the offset. Bangkok is 11 hours ahead of Eastern in the daylight period and 12 hours ahead in standard time, so a Bangkok midday is early morning in the east and the previous evening in the west. Enter the Bangkok date, not just the time, and the converter uses the US daylight saving rules in force on that date.
ICT is UTC+7 year-round: Thailand does not observe daylight saving time, so there is no ICT/IDT pair and no spring-forward or fall-back date to remember. UTC = Bangkok time − 7 hours. US times are then read from that UTC moment using the US zone rules in force on the entered date: Eastern is UTC−4 in daylight time and UTC−5 in standard time, Central UTC−5 / UTC−6, Mountain UTC−6 / UTC−7, Pacific UTC−7 / UTC−8. This converter works from the fixed Bangkok offset, never from a Bangkok daylight saving conversion, because there is none.
Setup: 12:00 ICT on October 24, 2026, when the US is on daylight time.
Line 1 — UTC. 12:00 − 7 hours = 05:00 UTC on October 24.
Line 2 — Eastern. 05:00 UTC − 4 hours (EDT) = 01:00 EDT on October 24.
Line 3 — Central. 05:00 UTC − 5 hours (CDT) = 00:00 CDT on October 24.
Line 4 — Mountain. 05:00 UTC − 6 hours (MDT) = 23:00 MDT on October 23 — the previous evening.
Line 5 — Pacific. 05:00 UTC − 7 hours (PDT) = 22:00 PDT on October 23.
Winter: 12:00 ICT on January 15, 2026. UTC is still 05:00, but the US has fallen back: 00:00 EST Eastern on January 15, 23:00 CST Central on January 14, 22:00 MST Mountain on January 14, and 21:00 PST Pacific on January 14. Every US time is one hour earlier than in October, even though the Bangkok time never moved.
The gap widens in winter. In the daylight period Bangkok sits 11 hours ahead of Eastern, 10 ahead of Central, 9 ahead of Mountain, and 8 ahead of Pacific. In standard time those gaps are 12, 11, 10, and 9 hours. The gap widens by 1 hour in winter because US clocks fall back while Bangkok stays put.
Why the date matters more than the time. Noon Bangkok time is 01:00 Eastern in October and 00:00 Eastern in January, and it crosses the US date line between Central and Mountain. A recurring meeting set by Bangkok time shifts on the US calendar twice a year, at the US daylight saving changes, even though nothing in Bangkok changes at all.
The date-change trap, stated plainly. Bangkok midday is early morning in the eastern US and the previous evening in the western US. If you book a "Friday" call from Bangkok without checking, your Pacific counterpart may be joining on Thursday night. Always read the US date the converter prints, not just the US clock time.
| Output | Formula | What it means |
|---|---|---|
| UTC | Bangkok time − 7 hours | 05:00 UTC at the defaults — the same moment on the world clock, every day of the year. |
| Eastern | UTC − 4 hours (EDT) / − 5 hours (EST) | 01:00 EDT on October 24 at the defaults; 00:00 EST on January 15 in winter. |
| Central | UTC − 5 hours (CDT) / − 6 hours (CST) | 00:00 CDT on October 24 at the defaults; 23:00 CST on January 14 in winter. |
| Mountain | UTC − 6 hours (MDT) / − 7 hours (MST) | 23:00 MDT on October 23 at the defaults; 22:00 MST on January 14 in winter. |
| Pacific | UTC − 7 hours (PDT) / − 8 hours (PST) | 22:00 PDT on October 23 at the defaults; 21:00 PST on January 14 in winter. |
The conversion is exact for the entered date and time, because the Bangkok offset never changes. The only subtlety is the US daylight saving transitions themselves: on the two US changeover Sundays, a US clock time near 2:00 a.m. may be ambiguous or skipped, and the converter reads the US zone from the UTC moment, which is the unambiguous way to resolve it. This is a converter, not a live clock: it converts the time you enter and does not track the current time. Error policy: malformed or out-of-range dates and times, and calendar dates that do not exist, are reported as errors rather than converted.
Bright Side Kit. "Bangkok Time Converter: ICT to US Time." https://brightoolbox.com/bangkok-time-converter/ Accessed October 24, 2026.No. Thailand stays on ICT, UTC+7, all year. There is no Thailand daylight time, no spring-forward, and no fall-back. That fixed offset is why the converter subtracts exactly 7 hours to reach UTC on every date.
23:00 ICT the same day in the daylight period, 00:00 ICT the next day in standard time. Bangkok is 11 hours ahead of Eastern in summer and 12 hours ahead in winter, because only the US moves.
Because the US falls back and Bangkok does not. 12:00 ICT is 01:00 EDT in October but 00:00 EST in January. The gap widens by 1 hour in winter on every US zone.
Yes, both share the UTC+7 offset. Hanoi is UTC+7 year-round, and Jakarta (western Indonesia time) is also UTC+7. Noon in Bangkok is noon in Hanoi, noon in Jakarta, and noon in Ho Chi Minh City.
UTC+7, always. Subtract 7 hours from any Bangkok time to get UTC: 12:00 ICT is 05:00 UTC on every day of the year, summer and winter alike.
No, it converts the time you enter. Enter the Bangkok date and time you care about — a meeting, a flight, a call — and it shows every zone at that same moment.
Yes, routinely in the west. Bangkok is far ahead of the western US, so Bangkok daytime is US evening of the previous day in Mountain and Pacific time. Always check the US date for Bangkok daytime calls, not just the clock.
Because US daylight saving rules depend on the date. Without the date the converter could not know whether the US is on daylight or standard time, and the answer would be off by an hour for half the year.