92 TimeLab — World Clock, Time Zone & Unix Timestamp Toolkit
One place to answer "what time is it there?" and plan across time zones.
See the time in up to four cities at once, convert a meeting across time zones with daylight saving handled correctly, convert Unix timestamps in any unit, and do calendar date math — all in one place, calculated locally in your browser.
What is a Unix timestamp?
A Unix timestamp (also called epoch time) is simply the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC. For example, 1735689600 is 2025-01-01T00:00:00Z — exactly 1,735,689,600 seconds after the epoch.
It carries no time zone information at all — it's just a count of seconds. That's what makes it so useful for computers: two systems anywhere in the world agree on exactly which instant a given timestamp means, even if they'd display it as a completely different local clock time. The 92 TimeLab timestamp tab converts between seconds, milliseconds, microseconds, and nanoseconds without losing precision, and shows that same instant in UTC, your own time zone, and every city you've selected.
UTC vs. GMT vs. local time
UTC(Coordinated Universal Time) is the precise scientific time standard the whole world's clocks are ultimately set from. It never changes for daylight saving.
GMT(Greenwich Mean Time) is, for almost every practical purpose, the same instant as UTC — but it's also the name of the local time zone used in the UK during winter, which does shift to BST in summer. That dual meaning is exactly why “GMT” gets used loosely and incorrectly in software: it's fine as a synonym for UTC, but it's a poor choice for a zone identifier.
Local time is UTC plus (or minus) whatever offset the relevant IANA zone — like Asia/Karachi or America/New_York— applies on that specific date. This is why 92 TimeLab always asks for a real place, not a raw offset: an offset like UTC+5 doesn't know when to change for daylight saving, but a proper zone identifier does.
Why does the time difference change?
Roughly 40% of countries observe daylight saving time for part of the year, and they don't all switch on the same date. For a few weeks each spring and autumn, one city in a conversation has already moved its clocks while the other hasn't — so a gap that's normally, say, 9 hours can briefly become 8 or 10.
92 TimeLab reads each zone's real offset for the exact date you've selected — not a fixed number — and flags a city on the world clock when its clocks recently changed or are about to. It also handles the two edge cases that trip up naive date math: the local hour that doesn't exist when clocks spring forward, and the local hour that happens twice when they fall back — asking you to pick the moment you meant instead of guessing silently.
Planning a meeting across time zones
Pick a date, time, and source city in the Converter & Planner tab, and every selected city updates to show that exact same moment — including its own local date, since a meeting that's 3 PM for you might already be tomorrow morning somewhere else.
Not sure what time actually works? Switch on “Find a good meeting time,” set normal working hours for each city, and it'll suggest slots where everyone's inside their working day — a starting point for the conversation, not a promise anyone's free. Once you've settled on a time, copy a plain-text summary, download a .ics file for your calendar, or copy a share link that reopens 92 TimeLab with the same cities and moment already set.
Common questions
What is a Unix timestamp?+
A Unix timestamp (or epoch time) is the number of seconds that have passed since January 1, 1970, 00:00:00 UTC. It's just a count of elapsed seconds — it has no time zone of its own. The clock time it represents depends entirely on which time zone you choose to display it in, which is why the same timestamp shows a different hour in Karachi, London, and New York.
What's the difference between seconds, milliseconds, microseconds, and nanoseconds?+
They're the same instant measured at different resolutions. Unix time is most commonly given in seconds (used by most APIs and databases) or milliseconds (used by JavaScript's Date.now()). Microseconds and nanoseconds show up in lower-level systems, logs, and some databases that need finer precision. 92 TimeLab keeps the exact value using BigInt math, so converting a very large microsecond or nanosecond timestamp never loses precision the way plain floating-point arithmetic can.
How does the time zone converter know the correct offset?+
It reads the offset your browser's built-in time zone database (the same one used by every modern browser and operating system) reports for that specific IANA zone on that specific date — not a hard-coded number. That's essential because offsets change: most zones shift by an hour for daylight saving part of the year, and some governments change their rules entirely. The offset shown is always the one that actually applied on the date you selected.
Why does the time difference between two cities sometimes change?+
Because not every zone observes daylight saving, and the ones that do don't all switch on the same date. For a few weeks each spring and autumn, one city has already changed its clocks while another hasn't — so a gap that's normally 9 hours might briefly become 8 or 10. 92 TimeLab flags a city with an upcoming or recent clock change so this doesn't catch you by surprise when planning ahead.
What happens if I pick a local time that doesn't exist, like during a daylight saving change?+
When clocks "spring forward," one hour of local time (say 2:00–2:59 AM) is skipped entirely and never happens. When they "fall back," an hour happens twice. 92 TimeLab detects both cases explicitly and asks you to pick which real moment you meant — the instant just before or after the skipped hour, or the earlier or later occurrence of a repeated one — instead of silently guessing.
How does the meeting planner suggest times?+
You set normal working hours for each selected city, and it scans the next two days in 30-minute steps for moments that fall inside everyone's working hours at once. These are suggestions based purely on the hours you enter — the tool has no idea about anyone's actual calendar, so treat the results as a starting point, not a guarantee.
Is my data uploaded anywhere?+
No. Every conversion, calculation, and lookup happens locally in your browser using standard Web APIs. Your selected cities and display preference are saved only in your own browser's local storage so they're there next time you visit — nothing is sent to 92 Nodes' servers.
Can I share a specific time with someone?+
Yes — the "Share link" button copies a URL that encodes your selected cities, time zone, and the exact chosen moment, so whoever opens it sees the same conversion. You can also download a .ics file to add that moment straight to a calendar app as a single, unambiguous event.
More free tools
Scheduling a recurring job instead of a meeting? The Cron Expression Builder previews run times against a chosen time zone too. Need the Hijri side of a date? The Islamic Calendar converts between Gregorian and Hijri dates. And for more free tools like this one, browse the full Developer Resources Directory.
More free resources
Have a project in mind? Let's build it.
Tell us about your goals and we'll get back to you within one business day with next steps.
Book a free call