Long Beach
United States · US
22:39:31
Timezone
America/Los_Angeles
Offset
GMT-7
Local date
Sat, May 30, 2026
Unix seconds
1780205971
Compare
Quick answer
Tokyo: +16h (Long Beach). 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.
United States · US
22:39:31
Timezone
America/Los_Angeles
Offset
GMT-7
Local date
Sat, May 30, 2026
Unix seconds
1780205971
Japan · JP
14:39:31
Timezone
Asia/Tokyo
Offset
GMT+9
Local date
Sun, May 31, 2026
Unix seconds
1780205971
| City | Local time | UTC offset | Work-hour status | Date relation |
|---|---|---|---|---|
| Long Beach | 22:39:31 | GMT-7 | Off hours | same day |
| Tokyo | 14:39:31 | GMT+9 | Work hours | Tokyo is next day |
Time difference
Tokyo +16h
Date relation
Tokyo is next day
Next shared work window
from Jun 1, 12:09 AM, about 60 min
Workday rule
09:00–18:00 local time
Tokyo: +16h (Long Beach). Check UTC offsets and date relation so midnight crossings are not missed.
Next shared work window: from Jun 1, 12:09 AM, about 60 min. If it is inconvenient, compare fair alternatives in the meeting planner.
Plan meetingAt least one city observes daylight saving time, so future dates can have a different offset than today. 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: Tokyo ⇄ Long Beach, +16h. Date relation.
Open timezone boardShared work window: from Jun 1, 12:09 AM, about 60 min. Work-hour status.
Open timezone boardCarry both cities into the planner: Long Beach / Tokyo. Date relation.
Plan meetingGoogle Calendar, Outlook, and ICS with named IANA time zones.
Build calendar linkShare this pair with the same context: Long Beach / Tokyo.
Open timezone boardTokyo: +16h (Long Beach). Current offset and date relation: Tokyo is next day.
Next shared work window: from Jun 1, 12:09 AM, about 60 min. Use the shared work window first. If it does not fit, compare another instant in the meeting planner.
Long Beach ↔ Tokyo: +16h. has daylight-saving risk on at least one side. Keep both IANA time zones and re-check transition weeks. America/Los_Angeles / Asia/Tokyo.
Verify the offset and date relation, open the same cities in the meeting planner, then publish Google Calendar, Outlook, and ICS links.