A time zone is a set of rules that determines the local civil time in a place. The simplest label is an offset from Coordinated Universal Time, or UTC. UTC+5:45 means local time is 5 hours and 45 minutes ahead of UTC: when it is 12:00 UTC, it is 5:45 PM there. UTC-4 means four hours behind: 12:00 UTC is 8:00 AM.
An offset alone is not always a complete time zone. “UTC-5” is a fixed difference, while “America/New_York” is a regional rule set that can use UTC-5 in standard time and UTC-4 during daylight saving time. For the current time in many places, use the world clock. For the concepts and lookup tools together, visit time zones.
Why time zones exist
Local time was once based mainly on the Sun: noon was near the moment the Sun reached its highest point. Because Earth rotates, solar noon occurs at different moments as longitude changes. Neighboring towns could therefore keep slightly different clock times. That was manageable when travel and communication were slow, but confusing for railway timetables and telegraph networks.
Standard time grouped regions under shared clock settings. The idealized world can be pictured as 24 one-hour bands, each about 15 degrees of longitude wide, because Earth rotates 360 degrees in roughly 24 hours. Real political borders, trade relationships, geography, and national choices bend those bands dramatically. A time-zone map is therefore a map of law and convention as much as astronomy.
What UTC means
UTC is the international reference used to coordinate clocks. Local times are expressed as differences from it. UTC itself does not move forward or backward for summer time. That stable reference lets an airline, server, or international team identify one instant without first agreeing on a local clock.
To read an offset, apply its sign to UTC. At 09:00 UTC, UTC+3 is 12:00 and UTC-7 is 02:00. A page such as UTC+3 shows places and current time for that offset. Be careful near midnight: adding hours can also advance the calendar date, while subtracting them can move to the previous date.
UTC versus GMT
Greenwich Mean Time, or GMT, is historically based on mean solar time at Greenwich. UTC is the modern atomic time standard used for international coordination. For ordinary civil-time conversion, GMT and UTC have the same zero-hour offset, so 3:00 GMT and 3:00 UTC indicate the same clock reading.
The terms are not interchangeable in every technical context. UTC is a standard; GMT is also used as the name of a time zone, particularly in the United Kingdom during winter and in some other places. When precision matters, write UTC and include a numeric offset or named regional zone.
How to read UTC+5:45
Split the label into hours and minutes. The plus sign means east, or ahead, relative to UTC; “5:45” is the amount to add. If an online meeting is at 14:00 UTC, a person at UTC+5:45 joins at 19:45 local time. If their local event is 08:00, subtract 5 hours 45 minutes to obtain 02:15 UTC.
For negative offsets, reverse the direction. At UTC-3:30, subtract 3 hours 30 minutes from UTC. Thus 10:00 UTC becomes 06:30 local. To convert local time back to UTC, add 3 hours 30 minutes. Writing the date beside every intermediate result prevents mistakes across midnight.
Why some offsets use 30 or 45 minutes
There is no physical law requiring civil zones to differ by whole hours. Governments select offsets that suit geography, history, national unity, and relationships with neighboring economies. India uses UTC+5:30; Nepal uses UTC+5:45. Parts of Australia use half-hour offsets, and the Chatham Islands use a 45-minute base offset.
These choices are unusual only compared with the whole-hour majority. They are fully valid zones. Scheduling software that assumes every offset is a whole number will be wrong, which is why robust systems store recognized zone rules rather than a hand-written list of hour differences.
| Place or zone | Standard offset | What makes it notable |
|---|---|---|
| India | UTC+5:30 | One half-hour standard for a large country |
| Nepal | UTC+5:45 | Quarter-hour offset |
| Newfoundland | UTC-3:30 | Half-hour standard; seasonal rules may apply |
| Eucla area, Australia | UTC+8:45 | Local quarter-hour convention |
| Chatham Islands | UTC+12:45 | Quarter-hour base; seasonal rules may apply |
| Marquesas Islands | UTC-9:30 | Half-hour offset west of UTC |
An offset is not a place
Many locations can share UTC+2 today and follow different rules later. One may remain fixed all year; another may move to UTC+3 for summer. Conversely, a city’s offset can change while its time-zone name remains the same. A named zone preserves the history and future rules needed to convert dates correctly.
Abbreviations such as CST are risky because they are not globally unique. The same letters may refer to different regions and offsets. Prefer a city, a recognized regional identifier, and an explicit date. “9:00 AM in Chicago on October 15” communicates more than “9:00 CST,” especially when daylight time may still be active.
Daylight saving changes the offset
Some jurisdictions advance clocks seasonally and later move them back. New York, for example, is generally UTC-5 in standard time and UTC-4 during daylight time. Rules differ by country and sometimes within a country. Arizona mostly does not follow the seasonal change even though most of the United States does.
This means a standing meeting between two cities may shift by an hour for several weeks if their transitions occur on different dates. Read the daylight-saving guide and check the actual cities on the relevant date rather than memorizing a difference.
How to convert time correctly
- Write the source place, local time, and full date.
- Find the source offset that applies on that date.
- Subtract the source offset to convert to UTC.
- Add the destination offset that applies at that same instant.
- Check whether the destination date moved backward or forward.
Example: a call at 6:00 PM in a UTC+2 location corresponds to 4:00 PM UTC. In a UTC-5 destination it is 11:00 AM. This arithmetic works only if +2 and -5 are the correct offsets for that date. The world clock is faster for current time; named-zone data is essential for future and historical dates.
The International Date Line
Near the opposite side of Earth from Greenwich, adjacent zones can have dates one calendar day apart. The International Date Line bends around national and island boundaries instead of following a perfectly straight longitude. Crossing it changes the calendar date, while the continuous passage of time does not jump.
For a remote meeting, always include weekday and date. “Monday at 9” may be Tuesday for another participant. Browse largest cities or world capitals to reach local clock pages, and use the days calculator when a date difference matters.
Travel and device clocks
Phones commonly obtain the local zone from the mobile network or location settings, but automatic detection can be disabled or delayed. After landing, compare the displayed city and offset before trusting an alarm. A fixed alarm may follow the new local time, while a calendar event tied to an instant may appear at a different local hour.
Keep travel confirmations with an explicit local time and airport. Departure and arrival times on tickets are normally displayed in each airport’s local time. The apparent flight duration cannot be found by simply subtracting those clock readings unless you first convert both to a common reference.
Fixed offsets and named zones in practice
A fixed offset is useful for aviation-style coordination, technical logs, and any rule that truly means the same distance from UTC all year. It is also easy to explain: UTC+3 never changes its arithmetic. A named zone is better when a human means the local civil clock in a real place, because that zone carries seasonal and historical changes.
Imagine scheduling “every day at 9:00 AM in London.” Storing only today’s offset can make the event appear at 10:00 after a seasonal change. Storing the London zone keeps it at the intended wall time while its UTC instant changes. For “run every 24 hours,” the desired behavior may be the opposite. State whether the promise concerns local clock time or elapsed duration.
Good habits for international scheduling
- Include the date, city, and numeric UTC offset in invitations.
- Use 24-hour time when AM and PM could be confused.
- Recheck future events after a government announces a rule change.
- Do not assume neighboring countries change clocks together.
- Store the named zone, not only the present offset, in software.
- Use countdowns for one shared deadline rather than separate local guesses.
Questions and answers
Is UTC+5:45 five hours and forty-five minutes ahead?
Yes. Add 5 hours 45 minutes to UTC to obtain local time, remembering that the calendar date may advance.
Are UTC and GMT the same?
They show the same zero-offset clock time for everyday use, but UTC is the modern international standard and GMT is also a historical and regional time-zone term.
Why can two cities with the same time today differ later?
They may follow different daylight-saving rules. A current numeric offset does not contain the future rule set of a named time zone.
What is the safest way to name a meeting time?
State the full date, local time, city or named zone, and UTC offset, then send a calendar invitation that recipients can view in their own zones.