Beijing
China · CN
00:00:00
Timezone
Asia/Shanghai
Offset
GMT+8
Local date
Mon, Jun 1, 2026
Unix seconds
1780243200
Compare
Quick answer
Siem Reap: -1h (Beijing). Confirm local times, UTC offsets, work-hour status, and date relation on this page. For meetings, start with the shared work window and then open the planner or calendar builder with the same cities and date.
China · CN
00:00:00
Timezone
Asia/Shanghai
Offset
GMT+8
Local date
Mon, Jun 1, 2026
Unix seconds
1780243200
Cambodia · KH
23:00:00
Timezone
Asia/Phnom_Penh
Offset
GMT+7
Local date
Sun, May 31, 2026
Unix seconds
1780243200
| City | Local time | UTC offset | Work-hour status | Date relation |
|---|---|---|---|---|
| Beijing | 00:00:00 | GMT+8 | Off hours | same day |
| Siem Reap | 23:00:00 | GMT+7 | Off hours | Siem Reap is previous day |
Time difference
Siem Reap -1h
Date relation
Siem Reap is previous day
Next shared work window
from Jun 1, 02:00 AM, about 480 min
Workday rule
09:00–18:00 local time
Siem Reap: -1h (Beijing). Check UTC offsets and date relation so midnight crossings are not missed.
Next shared work window: from Jun 1, 02:00 AM, about 480 min. If it is inconvenient, compare fair alternatives in the meeting planner.
Plan meetingNeither city has typical DST pressure today, but invites should still keep named IANA time zones. Build the final invite after choosing the exact date.
Build calendar linkThe live clocks show local time, offset, date relation, and overlap first. Then hand the same pair to the planner, board, or invite builder.
Offsets are current GMT differences; timezones are named rules that can shift with DST. For future meetings, keep the city timezone and selected instant together.
Same/next/previous day is calculated from each city’s local date, so it catches midnight crossings that a simple hour difference can hide.
DST can change this pair’s offset on another date. Use the meeting planner or calendar builder with a fixed time before sharing.
Workflow handoff
Keep the same cities and selected instant as you move from comparison to planning, board review, and invite creation.
Offset and date relation: Siem Reap ⇄ Beijing, -1h. Date relation.
Open timezone boardShared work window: from Jun 1, 02:00 AM, about 480 min. Work-hour status.
Open timezone boardCarry both cities into the planner: Beijing / Siem Reap. Date relation.
Plan meetingGoogle Calendar, Outlook, and ICS with named IANA time zones.
Build calendar linkShare this pair with the same context: Beijing / Siem Reap.
Open timezone boardSiem Reap: -1h (Beijing). Current offset and date relation: Siem Reap is previous day.
Next shared work window: from Jun 1, 02:00 AM, about 480 min. Use the shared work window first. If it does not fit, compare another instant in the meeting planner.
Beijing ↔ Siem Reap: has no typical DST shift pressure today, but calendar invites should still keep IANA time zones.
Verify the offset and date relation, open the same cities in the meeting planner, then publish Google Calendar, Outlook, and ICS links.