Current Time in Cambodia

About this tool

Cambodia runs on one clock: Indochina Time, UTC+7, with no daylight saving and no seasonal change, so the offset between Phnom Penh and anywhere else in the world is fixed all year. This page shows that time as a large digital readout with an analog face beside it, a date line, and a switch between the 24-hour and 12-hour formats. It is for the small decisions that depend on knowing whether it is a reasonable hour there: whether to ring a supplier in Phnom Penh before the office closes, whether a video call with a team in Siem Reap lands in their evening, whether a flight lands in time to reach a hotel before dark, or what time a market opens for someone trading across time zones. It reads the clock on the device you are using and converts it to Cambodia time; it does not contact a time server, does not claim to be an atomic clock, and cannot correct a device whose own clock is wrong. If you need several cities side by side, the world clock tool is the one to open.

How it works

`CurrentTimeCambodiaClient` in `current-time-cambodia-client.tsx` stores a `Date` in state, sets it once when the component mounts, and then replaces it every second through `setInterval(tick, 1000)`. The displayed value is not the raw local time of your device: `formatTimeCambodia` and `formatDateCambodia` in `format-date-time-khmer.ts` format that `Date` with `Intl.DateTimeFormat` and the constant `CAMBODIA_TZ`, which is the string `Asia/Phnom_Penh`. That is what makes the page show Phnom Penh time whether you are in Bangkok, London or New York, and it is also why the page never needs to know your own offset. The switch only changes the hour cycle passed to the formatter, so it cannot change the instant being shown. The analog face is drawn from the same `Date` and the same zone, and the offset label beside the clock is read from the formatter rather than hardcoded. There is no network request anywhere in the component: the whole page is the device clock plus a time zone conversion.

Use cases

• Deciding whether it is too late to call a supplier or a partner in Phnom Penh before the office closes
• Checking whether a video call with a team in Siem Reap falls inside their working day or their evening
• Working out what time a flight lands in Phnom Penh relative to a hotel check-in desk closing
• Confirming the local hour before a scheduled bank transfer cut-off or a market opening
• Planning a call with family in Cambodia from a different time zone without doing the arithmetic by hand
• Checking the Cambodian date when a deadline is quoted as a date rather than a time
• Teaching a class that includes students in Cambodia and needs a shared start time

Frequently asked questions

• What time zone does Cambodia use?

  Indochina Time, UTC+7, all year. The IANA time zone database identifies it as `Asia/Phnom_Penh` and gives it a constant offset of plus seven hours, which is the zone this page formats with. Thailand, Vietnam and Laos sit on the same offset, so a call between Phnom Penh and Bangkok needs no conversion at all.

• Where does the time on this page come from?

  From the clock of the device you are reading it on. The component calls `new Date()` and formats that value for the Cambodia zone; it never asks a server for the time. So the reading is only as correct as your own device, and a laptop whose clock has drifted will show Cambodia time with exactly the same drift. There is no network time sync on this page.

• How accurate is the display?

  Two limits. The device clock is the source, so any error in it is carried through unchanged. And the readout is refreshed by a one-second interval started when the page loaded, so it can sit up to about a second behind the true second boundary and it drifts by however long the tab was suspended. It is a clock to glance at, not a stopwatch for measuring an interval.

• Does Cambodia have daylight saving time?

  No. Cambodia has not observed daylight saving since the 1970s and the zone has no rules that shift it, so the offset is plus seven hours in January and in July alike. That is why this page has no summer and winter mode, and why a recurring meeting booked at 9am Phnom Penh time stays at the same absolute instant all year.

• Why does another clock show a different time for Cambodia?

  Usually one of two reasons. The other source may be reading your device clock too, in which case both are wrong together. Or it may be converting from a different zone because your operating system has the wrong region set, which moves the instant it thinks it is showing. This page always converts to `Asia/Phnom_Penh`, so a mismatch points at the device or the other tool, not at the offset.

• Is this the same as the world clock tool?

  No. This page shows one city and one zone, with a large readout and an analog face, and it is built for the single question of what time it is in Cambodia right now. The world clock tool lists several cities at once for comparison. Both read the same device clock and both are limited by it, so they should never disagree about Phnom Penh.

• Does the 12-hour or 24-hour switch change the time?

  No. It changes only how the same instant is written: 17:30 becomes 5:30 PM. Cambodia uses the 24-hour clock in timetables, government notices and transport, while 12-hour time is common in speech and in shops. The switch is a display preference and is not remembered between visits, so the page opens in 24-hour format each time.

• Does the page work without a connection?

  Once it has loaded, yes. The component makes no network request for the time, so nothing breaks when the connection drops: the readout keeps advancing from the device clock. The page itself still has to be fetched the first time, and a hard reload while offline will fail. Nothing about the reading is cached from a previous visit.

Data and accuracy

Content last reviewed 21 October 2026