Read the sign from UTC toward the local clock
UTC+05:30 means the local clock is five hours and thirty minutes ahead of UTC at that instant. UTC−04:00 means it is four hours behind. The sign belongs to the offset, not to the direction in which you happen to read a city comparison.
Keep the arithmetic attached to a date
At 13:00 UTC on 27 October 2026, adding five hours and thirty minutes gives 18:30 in Mumbai. Subtracting four hours gives 09:00 in New York. Adding eleven hours gives 00:00 on 28 October in Sydney. The final example crosses midnight, so the date must change along with the hour.
| City | Offset at this instant | Local date and time |
|---|---|---|
| New York | UTC−04:00 | 27 October · 09:00 |
| Mumbai | UTC+05:30 | 27 October · 18:30 |
| Sydney | UTC+11:00 | 28 October · 00:00 |
An offset is a result, not a complete rule
New York’s offset is UTC−04:00 in that example and UTC−05:00 on 3 November 2026. America/New_York is the named rule identifier that determines which offset applies. Storing only the October offset would not preserve a weekly New York wall-time instruction through the change.
An abbreviation is also a display aid. Short forms can be reused in unrelated places and may change seasonally. When someone gives you only “CST” or “Pacific time,” ask for a city or exact named zone and the intended date.
Check the end time too
A ninety-minute event starting at 13:00 UTC ends at 14:30 UTC. In the Mumbai row that becomes 18:30–20:00. A displayed working-hours interval must contain both ends. The offset arithmetic can be correct while the meeting still extends past the availability someone offered.
Let display preferences stay in the display
The same 18:30 local time can be shown as 6:30 PM. A 12-hour preference should not change the saved instant, the ISO date, or the calendar timestamp. Use the planner’s readable rows for discussion and its resolved calendar export to carry the event to another application.
Sources
Follow the original references for the rules and formats used in this guide.