ICT — Indochina Time
Current time, offset and daylight saving status for Indochina Time.
Current time in ICT
21:12:26
Indochina Time · UTC+07:00
About ICT
Indochina Time covers Thailand, Vietnam, Cambodia, Laos and western Indonesia.
Working with ICT
UTC+07:00 applies here on every date of the year — there is no summer offset for Indochina Time to switch to, so a time written against it means the same instant in January as in July.
When it is noon UTC, Indochina Time reads 19:00; midnight UTC is 07:00 here. ICT runs 7 h ahead of UTC, so its calendar day begins before the reference clock’s does.
No other zone in this directory keeps UTC+07:00 as its standard offset. One hour to the west of ICT in this directory sits BST (BD) (UTC+06:00); one hour to the east, CST (China) (UTC+08:00).
Clock changes in ICT
Indochina Time has no clock change at any point in the year; UTC+07:00 applies on every date, in Bangkok as everywhere else on the zone.
Of the reference zones in the table below, New York, London, Berlin, Sydney and Los Angeles observe daylight saving, so their difference from ICT shifts twice a year; UTC, Dubai, Kolkata, Singapore and Tokyo stay fixed.
Where ICT is used
In this directory one city keeps ICT: Bangkok. Between them they cover Thailand.
Where ICT stands today
Indochina Time is UTC+07:00 today and will be UTC+07:00 on every other day. A recurring meeting anchored to ICT never drifts against UTC, which makes it a dependable reference for logs kept in Bangkok and for schedules that run across a whole year.
A working day on ICT
Taking Bangkok as the reference point for ICT, and a working day as 09:00 to 17:00:
- New York has no overlap at all: when it is 09:00 there, it is already 20:00 in Bangkok, so a call means an early start or a late finish for someone.
- London overlaps for only 2 hours, from 15:00 to 17:00 Bangkok time — late in the day at one end and early at the other.
- Tokyo’s working day overlaps with Bangkok’s for 6 hours, from 09:00 to 15:00 Bangkok time.
On the June solstice the sun rises in Bangkok at about 05:51 and sets at about 18:47; on the December solstice it rises at about 06:36 and sets at about 17:55.
How ICT compares with other zones
Right now ICT runs ahead of UTC, New York, London, Berlin, Dubai, Kolkata and Los Angeles and behind Singapore, Tokyo and Sydney.
| Zone | UTC offset | Difference from ICT |
|---|---|---|
| UTC | UTC+00:00 | 7h ahead |
| New York | UTC-04:00 | 11h ahead |
| London | UTC+01:00 | 6h ahead |
| Berlin | UTC+02:00 | 5h ahead |
| Dubai | UTC+04:00 | 3h ahead |
| Kolkata | UTC+05:30 | 1h 30m ahead |
| Singapore | UTC+08:00 | 1h behind |
| Tokyo | UTC+09:00 | 2h behind |
| Sydney | UTC+11:00 | 4h behind |
| Los Angeles | UTC-07:00 | 14h ahead |
Larger places currently keeping ICT: Thailand.
Cities using ICT
Convert ICT to another zone
Related time zones
Time zone rules: IANA tz database release 2026c, applied when this page was generated on 2026-10-09.
Frequently asked questions
What is ICT?
Indochina Time, ICT, is UTC+07:00. Indochina Time covers Thailand, Vietnam, Cambodia, Laos and western Indonesia.
What is the IANA identifier for ICT?
Asia/Bangkok — the entry that covers Bangkok in the tz database. Use it rather than ICT in software: ICT names one season, Asia/Bangkok names the rules for every date.
Does ICT change for daylight saving?
No. Indochina Time keeps UTC+07:00 on every date; no other listed zone keeps that offset.
How do I convert ICT to my local time?
One hour to the west of ICT in this directory sits BST (BD) (UTC+06:00); one hour to the east, CST (China) (UTC+08:00). For anything beyond that, the converter applies the rules of Asia/Bangkok for the date you give it rather than a remembered figure.
Which cities use ICT?
In this directory one city keeps ICT: Bangkok. Between them they cover Thailand. The boundary is legal rather than geographic: it follows the borders of Thailand, not a line of longitude.
What should I put in a configuration file for ICT?
Asia/Bangkok, never ICT. That entry carries the rules Bangkok actually follows, including when daylight saving starts and ends, so software using it stays correct through a change that a stored offset would miss.