---
title: "What is IST (India Standard Time)?"
url: https://meet.barq.dev/glossary/ist-india-standard-time
updated: 2026-11-17
author: "Hammad Ali"
---

# What is IST (India Standard Time)?

> **Short answer:** IST, meaning India Standard Time here, is the local time represented by Asia/Kolkata in a scheduling system, with a calculated offset of UTC+05:30 on 17 November 2026. On that date, 09:00 there is 03:30 UTC; spell out India and the date when proposing a meeting, because an abbreviation alone leaves room for mistakes.


## How does India Standard Time convert to UTC?

For the date calculated here, subtract five hours and thirty minutes from an Asia/Kolkata clock reading to get UTC. Treating a half-hour offset as five whole hours would put the same meeting thirty minutes away from its intended start. Keep the minutes.


We calculated these examples with Luxon using the IANA identifier Asia/Kolkata, with explicit local dates instead of a manually shifted clock. The [IANA time-zone database](https://www.iana.org/time-zones) and its [release notes](https://data.iana.org/time-zones/tzdb/NEWS) are the sources identified in our research, checked as of 17 Nov 2026.


| India local date and time | UTC date and time | Calculation |
| --- | --- | --- |
| 17 Nov 2026, 09:00 | 17 Nov 2026, 03:30 | 09:00 minus 05:30 |
| 17 Nov 2026, 17:30 | 17 Nov 2026, 12:00 | 17:30 minus 05:30 |

These are dated conversions, not a table of historical rules. The [time-zone abbreviation reference](https://meet.barq.dev/glossary/time-zone-abbreviations) explains why a city-based identifier carries more scheduling information than a short label.


## Why can a half-hour offset change the offered starts?

A half-hour offset means a start on the hour in one zone can appear on the half-hour in another. In the worked example, a 09:00 India appointment appears at 03:30 UTC even though both guests are looking at the same instant. Neither display is wrong.


For an email proposal, write "17 November 2026, 09:00 India time (Asia/Kolkata)" and include the duration. Don't write only "9 IST" and expect the reader to supply the date, country and morning-or-evening choice.


A thirty-minute call beginning at that time ends at 09:30 India time, or 04:00 UTC. The offset changes the labels, not the thirty minutes you've agreed to spend together.


## How does Barq Meet handle India-time bookings?

Barq Meet associates availability with a named schedule time zone and shows offered times in the guest's selected zone. A host can set their working hours around India time while a guest reads the resulting appointment in their own local clock. Check both sides. The [Gulf Standard Time definition](https://meet.barq.dev/glossary/gst-gulf-standard-time) gives the clock reference while leaving each participant's actual working days to be checked separately.


We let you create multiple schedules when different offers need different hours. We also recheck selected Google calendars at confirmation, so a conversion doesn't make an occupied interval bookable.


The host needs Google Calendar; connecting an Outlook calendar isn't supported. A guest can still open the public booking page without adopting the host's time zone.


## Which terms should I read alongside IST?

Read the abbreviation entry for naming, and the scheduling glossary for availability concepts. The IST meaning in this entry is India Standard Time; a bare acronym in someone else's invitation shouldn't be treated as a complete time-zone definition. Use the date every time.


The [scheduling glossary](https://meet.barq.dev/glossary/scheduling-glossary) is the term index; the [cross-zone scheduling guide](https://meet.barq.dev/guides/scheduling-across-time-zones) puts those definitions into a booking setup. Review [account pricing and calendar limits](https://meet.barq.dev/pricing), then [set up a booking page with a named time zone](https://meet.barq.dev/app/sign-in) if you're coordinating across clocks.

## Frequently asked questions

### Is 09:00 India time the same as 09:00 UTC?

No. In the 17 November 2026 calculation here, 09:00 in Asia/Kolkata is 03:30 UTC. Use the date and named zone for a conversion instead of copying the same clock reading into an invitation labeled UTC. Keep the half-hour offset in the arithmetic, because treating India as a whole-hour difference can place the call thirty minutes late.

### Should I round an India-time appointment to the hour?

No. Keep the exact converted minutes. A half-hour offset can turn an on-the-hour start into a half-hour start in another zone; rounding it changes the appointment itself, even if the rounded time looks tidier. Use the converted start exactly as agreed and inspect its full date, instead of rounding the appointment to simplify the displayed hour.

### What should I do if someone writes only IST?

Ask which country or named time zone they mean, and confirm the meeting date. This page uses IST for India Standard Time, but an isolated abbreviation isn't enough information to resolve every invitation safely. Ask for the city and date before converting, so an abbreviation shared by several regions doesn't determine the invitation's start incorrectly.

## Related pages

- [Time zone abbreviations list for scheduling](https://meet.barq.dev/glossary/time-zone-abbreviations)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)
- [How to schedule meetings across time zones](https://meet.barq.dev/guides/scheduling-across-time-zones)
- [What is GST (Gulf Standard Time)?](https://meet.barq.dev/glossary/gst-gulf-standard-time)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
