Timezone converter
UTC to IST currently uses Coordinated Universal Time (UTC) in Etc/UTC and India Time in Asia/Kolkata as the live reference pair, with a +5h 30m live gap. UTC to IST matters whenever Etc/UTC and Mumbai need to coordinate across a +5h 30m gap. The UTC side covers the listed reference zone, while IST covers India and Israel — that country mix is the practical reason this conversion shows up in calendars rather than the abstract offset math.
Offset math, DST behavior, and city coverage on both sides are refreshed from the live timezone dataset during the page revalidation window.
IST is ambiguous in this dataset, so the live converter uses Asia/Kolkata as the busiest reference zone while the city list below shows the wider label family.
From
Coordinated Universal Time (UTC)
Etc/UTC · UTC +00:00
This grouping is currently anchored by the reference zone Etc/UTC.
To
India Time
Asia/Kolkata · GMT+5:30 +05:30
Major markets in this grouping include Mumbai, Delhi, Bengaluru, Hyderabad.
Current gap
+5h 30m
UTC +00:00 vs IST +05:30
9-to-5 overlap
2.5h
UTC 9:00 AM previous day to 11:30 AM previous day
Representative countries
No country breakdown available / India, Israel, and Sri Lanka
Based on the busiest city and zone usage found in the current dataset.
UTC (Etc/UTC, +00:00) to IST (Mumbai, +05:30) is currently a +5h 30m conversion. Live coverage on the UTC side is anchored by Etc/UTC; the IST side draws from Mumbai, Delhi, Bengaluru, and Hyderabad.
UTC to IST matters whenever Etc/UTC and Mumbai need to coordinate across a +5h 30m gap. The UTC side covers the listed reference zone, while IST covers India and Israel — that country mix is the practical reason this conversion shows up in calendars rather than the abstract offset math.
The pair sits +5h 30m apart across Other and Asia, which usually allows a meaningful shared workday on at least one end.
Neither UTC nor IST observes daylight saving on the reference zones used here, so the gap stays steady all year. That makes this pair predictable for recurring meetings, broadcast schedules, and contracts that care about a stable offset.
UTC and IST sit 5h 30m apart, with about 2.5h of shared 9-to-5 time. That is enough room for one daily standup plus one focused working session, which is what most cross-region teams actually use this overlap for.
Reference zone, current offsets, country and city anchors, overlap math, and date-shift answers for UTC to IST.
Reference pair
Etc/UTC -> Asia/Kolkata
Live offsets
UTC +00:00 vs IST +05:30
Meaning split
Coordinated Universal Time (UTC) / India Time
Country anchors
No country breakdown available -> India, Israel, and Sri Lanka
City anchors
Etc/UTC -> Mumbai, Delhi, Bengaluru, Hyderabad
Workday overlap
2.5h window: UTC 9:00 AM previous day-11:30 AM previous day
Morning answer
9 AM UTC = 2:30 PM IST, same day
Evening answer
6 PM UTC = 11:30 PM IST, same day
Same-offset labels can share the same hour while still landing in different countries, calendars, cities, and workday windows. These notes show the practical context behind this conversion.
UTC to IST is pinned to Etc/UTC -> Asia/Kolkata, with the shorthand labels shown as context. The city anchors are Etc/UTC on the UTC side and Mumbai, Delhi, Bengaluru, Hyderabad on the IST side, with +5h 30m between the live reference zones.
The 12 popular-hour answers include 11 same-day conversions, 1 next-day conversions, and 0 previous-day conversions. That distribution is what separates this page from a static offset chart.
Nearby labels sharing a current offset include GMT (From side), WEST (From side), WET (From side). They may match mathematically, but their country calendars, city anchors, and common search intent differ from this exact pair.
UTC: ; 0 mapped cities; languages unavailable; currency unavailable | IST: India (IN); 3776 mapped cities; capital New Delhi; English, Hindi, Tamil; INR Indian rupee | IST: Israel (IL); 108 mapped cities; capital Jerusalem; Arabic, Hebrew; ILS Israeli new shekel | IST: Sri Lanka (LK); 60 mapped cities; capital Sri Jayawardenepura Kotte; Sinhala, Tamil; LKR Sri Lankan rupee
Offset behavior, DST gap changes, local calendar evidence, and the day-shift pattern across the most common conversion hours.
UTC/IST is a regional or transcontinental offset gap: Etc/UTC currently reads +00:00, Asia/Kolkata reads +05:30, and the live delta is +5h 30m. This class decides whether the page behaves like a same-day planner or a handoff planner.
Etc/UTC and Asia/Kolkata do not show a detected near-term DST gap-change note in this sample, but the page still exposes exact IANA zones so users do not treat the abbreviation pair as permanently fixed.
No country holiday snapshot is attached to this exact pair yet, so the page leans on city anchors, IANA zones, offsets, and the live conversion table instead of pretending a local calendar exists.
Across the 12 popular-hour answers, this pair has 11 same-day answers, 1 next-day answers, 0 previous-day answers. That mix is specific to the current Etc/UTC -> Asia/Kolkata relationship and helps users see whether dates must be written explicitly in invites, travel plans, and release schedules.
Same-offset converter clusters can look identical if the page only shows a numeric offset. This audit states whether the route should be indexed, which canonical peer it follows when consolidated, and what pair-specific evidence keeps the page useful.
This pair remains indexable because the route has enough pair-specific context: Etc/UTC -> Asia/Kolkata, country anchors, city anchors, calendar notes, and day-shift examples.
UTC and IST are not currently a same-offset pair; the live delta is +5h 30m. Same-offset neighbors are still listed because users often confuse nearby abbreviations.
GMT (From side, +00:00), WEST (From side, +00:00), WET (From side, +00:00) The page keeps these labels visible so SGT/HKT/GST-style clusters do not blur into one generic offset page.
UTC/IST uses 11 same-day answers, 1 next-day answers, 0 previous-day answers; 2.5h strict workday overlap; source zones Etc/UTC and Asia/Kolkata; country anchors No country breakdown available -> India, Israel, and Sri Lanka.
Common places, calendars, markets, languages, and operating contexts behindUTC and IST.
UTC
UTC is the neutral technical baseline used for servers, APIs, logs, aviation-adjacent timestamps, and global release notes. It is not a local civil calendar, so the receiving side of a conversion carries the real holiday, language, market, and business-hour context.
UTC
When UTC is paired with a local abbreviation, the useful question is not only the offset. It is whether the local side lands on a business day, a holiday, a same-day handoff, or an overnight date shift.
Same-offset conversions can still land in different public-holiday, language, currency, and city-anchor contexts. These rows use the country profile and holiday snapshots behind each side of the pair.
IST
3,776 mapped city anchors; zones Asia/Kolkata.capital New Delhi; English, Hindi, Tamil; INR Indian rupee
Holiday snapshot: Republic Day (Jan 26, Public) · Holi (Mar 4, Public) · Eid al-Fitr (Mar 21, Public) · Mahavir Jayanti (Mar 31, Public) · Good Friday (Apr 3, Public)
IST
108 mapped city anchors; zones Asia/Jerusalem.capital Jerusalem; Arabic, Hebrew; ILS Israeli new shekel
Holiday snapshot: No holiday snapshot attached for the current year.
IST
60 mapped city anchors; zones Asia/Colombo.capital Sri Jayawardenepura Kotte; Sinhala, Tamil; LKR Sri Lankan rupee
Holiday snapshot: No holiday snapshot attached for the current year.
Pair-specific dossier
UTC to IST is usually a technical or operations conversion: a log line, release timestamp, incident window, cron job, or API event needs to become a local civil time. The hard part is not UTC; it is IST, which can mean India, Ireland, or Israel.
For India, UTC to IST adds five hours and thirty minutes, and India does not currently observe DST. For Irish Standard Time or Israel Standard Time, the offset and seasonal behavior differ. This is why the page should force the city/IANA-zone check before encouraging any human planning.
The page is especially useful for engineering, SRE, support, and incident-response teams because UTC is excellent for ordering events, while IST is needed for staffing and calendar interpretation.
Most often used by technical teams converting neutral UTC timestamps into India local time, while preserving disambiguation for Irish and Israeli IST contexts.
For India, 00:00 UTC is 05:30 IST and 18:30 UTC is midnight the next day in India. That half-hour boundary matters for incident reports, payroll runs, SLO windows, and customer-support staffing.
UTC has no holidays; the receiving civil timezone does. India, Ireland, and Israel have different public calendars, weekend norms, and DST policies, so the target meaning must be resolved before the availability check.
Not the same as UTC/GMT when the target is a person or office. UTC is neutral; IST is a civil-time abbreviation with multiple meanings.
Three-letter abbreviations are ambiguous. The IANA zone identifier above is the canonical reference; software, contracts, and calendar storage should use it instead of the abbreviation.
These are the labels most likely to be confused with either side of this conversion. A matching UTC offset does not mean the same country, calendar, market, source convention, or user intent.
UTC and GMT match on offset right now, but the page should not collapse them: they carry different city anchors, country calendars, currencies, holidays, and user intent.
UTC and WEST match on offset right now, but the page should not collapse them: they carry different city anchors, country calendars, currencies, holidays, and user intent.
UTC and WET match on offset right now, but the page should not collapse them: they carry different city anchors, country calendars, currencies, holidays, and user intent.
UTC and AZOST are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
UTC and AZOT are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
UTC and CEST are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
IST and IOT are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
IST and AFT are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
IST and BST are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
IST and BTT are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
IST and CCT are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
IST and FSAT are close enough to be confused in search, but they are not the same clock label and should be pinned to exact IANA zones.
Abbreviations with the same UTC offset can still represent different countries, cities, currencies, languages, and civil-time histories. This roster keeps theUTC to IST page grounded in those concrete places.
UTC: ; 0 mapped cities; zones Etc/UTC; city anchors not listed; country-profile snapshot unavailable.
IST: India (IN); 3776 mapped cities; zones Asia/Kolkata; city anchors Mumbai (Asia/Kolkata, pop 12,691,836), Delhi (Asia/Kolkata, pop 11,034,555), Bengaluru (Asia/Kolkata, pop 8,495,492), Hyderabad (Asia/Kolkata, pop 6,993,262); official Republic of India; capital New Delhi; region Asia; subregion Southern Asia; population 1,417,492,000; area 3,287,263 km2; languages English, Hindi, Tamil; currency INR Indian rupee.
IST: Israel (IL); 108 mapped cities; zones Asia/Jerusalem; city anchors Jerusalem (Asia/Jerusalem, pop 971,800), Tel Aviv (Asia/Jerusalem, pop 432,892), West Jerusalem (Asia/Jerusalem, pop 400,000), Haifa (Asia/Jerusalem, pop 285,316); official State of Israel; capital Jerusalem; region Asia; subregion Western Asia; population 10,134,800; area 21,937 km2; languages Arabic, Hebrew; currency ILS Israeli new shekel.
IST: Sri Lanka (LK); 60 mapped cities; zones Asia/Colombo; city anchors Colombo (Asia/Colombo, pop 648,034), Dehiwala-Mount Lavinia (Asia/Colombo, pop 219,827), Maharagama (Asia/Colombo, pop 195,355), Jaffna (Asia/Colombo, pop 169,102); official Democratic Socialist Republic of Sri Lanka; capital Sri Jayawardenepura Kotte; region Asia; subregion Southern Asia; population 21,763,170; area 65,610 km2; languages Sinhala, Tamil; currency LKR Sri Lankan rupee.
Same-offset converter pages can look deceptively alike. These records pin the page to the exact abbreviations, IANA zones, countries, and city anchors behind UTC and IST.
UTC (utc) is not marked ambiguous in the abbreviation catalog. Meaning records: Coordinated Universal Time (UTC) at UTC+00:00; listed zones Etc/UTC; source label Coordinated Universal Time (UTC).
UTC currently maps to 1 country footprint in the converter dataset: none listed. The footprint spans 1 IANA zone across 0 city anchors.
UTC: ; 0 mapped cities; zones Etc/UTC; city anchors not listed; country-profile snapshot unavailable.
IST (ist) is ambiguous in the abbreviation catalog. Meaning records: Israel Time at UTC+02:00; listed zones Asia/Jerusalem; source label Israel Time - Jerusalem, Tel Aviv, West Jerusalem, Haifa | India Time at UTC+05:30; listed zones Asia/Colombo; Asia/Kolkata; source label India Time - Colombo, Dehiwala-Mount Lavinia, Maharagama, Jaffna.
IST currently maps to 3 country footprints in the converter dataset: India (IN), Israel (IL), Sri Lanka (LK). The footprint spans 3 IANA zones across 10 city anchors.
IST city anchors in this indexed page family: Mumbai [mumbai-IN, IN, Asia/Kolkata, pop 12,691,836]; Delhi [delhi-IN, IN, Asia/Kolkata, pop 11,034,555]; Bengaluru [bengaluru-IN, IN, Asia/Kolkata, pop 8,495,492]; Hyderabad [hyderabad-IN, IN, Asia/Kolkata, pop 6,993,262]; Ahmedabad [ahmedabad-IN, IN, Asia/Kolkata, pop 6,357,693]; Chennai [chennai-IN, IN, Asia/Kolkata, pop 4,681,087]; Kolkata [kolkata-IN, IN, Asia/Kolkata, pop 4,631,392]; Surat [surat-IN, IN, Asia/Kolkata, pop 4,591,246]; Pune [pune-IN, IN, Asia/Kolkata, pop 3,124,458]; Jaipur [jaipur-IN, IN, Asia/Kolkata, pop 3,046,163].
IST: India (IN); 3776 mapped cities; zones Asia/Kolkata; city anchors Mumbai (Asia/Kolkata, pop 12,691,836), Delhi (Asia/Kolkata, pop 11,034,555), Bengaluru (Asia/Kolkata, pop 8,495,492), Hyderabad (Asia/Kolkata, pop 6,993,262); official Republic of India; capital New Delhi; region Asia; subregion Southern Asia; population 1,417,492,000; area 3,287,263 km2; languages English, Hindi, Tamil; currency INR Indian rupee. IST: Israel (IL); 108 mapped cities; zones Asia/Jerusalem; city anchors Jerusalem (Asia/Jerusalem, pop 971,800), Tel Aviv (Asia/Jerusalem, pop 432,892), West Jerusalem (Asia/Jerusalem, pop 400,000), Haifa (Asia/Jerusalem, pop 285,316); official State of Israel; capital Jerusalem; region Asia; subregion Western Asia; population 10,134,800; area 21,937 km2; languages Arabic, Hebrew; currency ILS Israeli new shekel. IST: Sri Lanka (LK); 60 mapped cities; zones Asia/Colombo; city anchors Colombo (Asia/Colombo, pop 648,034), Dehiwala-Mount Lavinia (Asia/Colombo, pop 219,827), Maharagama (Asia/Colombo, pop 195,355), Jaffna (Asia/Colombo, pop 169,102); official Democratic Socialist Republic of Sri Lanka; capital Sri Jayawardenepura Kotte; region Asia; subregion Southern Asia; population 21,763,170; area 65,610 km2; languages Sinhala, Tamil; currency LKR Sri Lankan rupee.
UTC is the neutral baseline used by servers, APIs, aviation, and software logs. Unlike city-based civil time labels, it is a reference standard first and a local clock label second, which is why timestamps stored as UTC stay correct even when local rules change. This page uses Etc/UTC as the live reference at +00:00 (UTC). UTC works more as a reference label here than as a city-anchored civil-time label, so the IANA zone is what carries the practical weight. UTC is stable on Etc/UTC year-round, with no seasonal clock changes in the next year. That makes it a low-friction choice for recurring meetings and broadcast schedules — but software still prefers the IANA zone because governments can change civil-time rules independently of the short code.
UTC is not heavily split in the current catalog, but the short label still hides the underlying IANA zone and any future policy change. The safe pattern is to write the abbreviation for humans and the zone for machines. Etc/UTC sits on UTC year-round in current rules, which makes UTC unusually stable for cross-system timestamps. Even so, civil-time policy can change, so an explicit zone reference is still the safest store. UTC works well as a global baseline, but it does not tell you whether a local place follows daylight saving time. That is why city pages still need IANA zones — UTC is the storage primitive, not the local-clock answer.
UTC should not be blindly swapped with nearby labels. Adjacent references in the catalog: GMT (+00:00, Often compared as a zero-offset reference); WEST (+00:00, Currently sits on the same UTC offset); WET (+00:00, Currently sits on the same UTC offset); AZOST (-01:00, Runs on a nearby UTC offset); AZOT (-01:00, Runs on a nearby UTC offset); CEST (+01:00, Runs on a nearby UTC offset).
UTC has 1 meaning record, offset range UTC+00:00, labels Coordinated Universal Time (UTC), and 0 country footprints across 1 IANA zone.
IST is reused across 2 different meanings in this dataset — India Time and Israel Time — which is why the short code alone is not enough to identify a place. Each meaning maps to its own IANA zone family and its own DST behavior, and they happen to share the same letters by historical accident more than by design. The busiest cities using IST in the current catalog are Mumbai, Delhi, Bengaluru, Hyderabad, and Ahmedabad. The lead live reference on this page is Mumbai (Asia/Kolkata), currently at +05:30 (GMT+5:30). Those cities are what give IST its actual feel rather than the abstract offset. Because IST spans UTC+02:00 to UTC+05:30 across the active meanings, software, calendars, and contracts should always pin a specific IANA zone such as Asia/Kolkata or a literal UTC offset. The short label is fine for headlines and chat; it is the wrong primitive for storing or scheduling timestamps.
IST appears with 2 distinct meanings in current data, splitting across UTC+02:00 to UTC+05:30. The short label looks tidy in writing but quietly hides which place you mean — pick a city, a country, or an IANA zone before it matters. Asia/Kolkata does not show an offset change in the next year, which makes IST predictable for short-term scheduling. Predictable is not the same as permanent — civil-time rules still get changed by governments on relatively short notice. For precise work, the safest equivalent of IST is the exact IANA zone used by your city or system. Asia/Kolkata sits at +05:30, ahead of UTC, which means daily logs in this zone reach a new calendar date before UTC does — a small detail that breaks date-based reporting if missed.
IST should not be blindly swapped with nearby labels. Adjacent references in the catalog: IOT (+06:00, Runs on a nearby UTC offset); AFT (+04:30, Runs on a nearby UTC offset); BST (+06:00, Runs on a nearby UTC offset); BTT (+06:00, Runs on a nearby UTC offset); CCT (+06:30, Runs on a nearby UTC offset); FSAT (+05:00, Runs on a nearby UTC offset).
IST has 2 meaning records, offset range UTC+02:00 to UTC+05:30, labels India Time, Israel Time, and 3 country footprints across 3 IANA zones.
IST country anchor India: India, officially the Republic of India, is a country in South Asia. It is the seventh-largest country by area; the most populous country since 2023; and, since its independence in 1947, the world's most populous democracy. Bounded by the Indian Ocean on the south, the Arabian Sea on the southwest, and the Bay of Bengal on the southeast, it shares land borders with Pakistan to the west; China, Nepal, and Bhutan to the north; and Bangladesh and Myanmar to the east. In the Indian Ocean, India is near Sri Lanka and the Maldives. Its Andaman and Nicobar Islands share a maritime border with Myanmar, Thailand, and Indonesia. Source: Wikipedia.
UTC is the neutral technical baseline used for servers, APIs, logs, aviation-adjacent timestamps, and global release notes. It is not a local civil calendar, so the receiving side of a conversion carries the real holiday, language, market, and business-hour context.
When UTC is paired with a local abbreviation, the useful question is not only the offset. It is whether the local side lands on a business day, a holiday, a same-day handoff, or an overnight date shift.
UTC/IST uses Etc/UTC -> Asia/Kolkata, offset delta +5h 30m, overlap 2.5h, route /convert/utc/ist/, and live abbreviation readings UTC/GMT+5:30.
IST coverage is led by Mumbai, India, Delhi, India, Bengaluru, India, and Hyderabad, India, with 2 more anchoring the wider label family. Combined with the UTC side, this conversion ends up describing cross-region coordination that uses the morning-on-one-side, afternoon-on-the-other window for live work.
Adjust the time. Digits roll like an odometer, and the swap button flips the zones.
Same day in both places.
Quick conversions for 9 AM, noon, 3 PM, 6 PM, and 9 PM based on today's local calendar.
| UTC | IST | Day relation |
|---|---|---|
| 9:00 AM | 2:30 PMThu, Nov 5 | same day |
| 12:00 PM | 5:30 PMThu, Nov 5 | same day |
| 3:00 PM | 8:30 PMThu, Nov 5 | same day |
| 6:00 PM | 11:30 PMThu, Nov 5 | same day |
| 9:00 PM | 2:30 AMFri, Nov 6 | next day |
Quick conversions for 9 AM, noon, 3 PM, 6 PM, and 9 PM based on today's local calendar.
| IST | UTC | Day relation |
|---|---|---|
| 9:00 AM | 3:30 AMFri, Nov 6 | same day |
| 12:00 PM | 6:30 AMFri, Nov 6 | same day |
| 3:00 PM | 9:30 AMFri, Nov 6 | same day |
| 6:00 PM | 12:30 PMFri, Nov 6 | same day |
| 9:00 PM | 3:30 PMFri, Nov 6 | same day |
UTC to IST ranges from UTC 9:00 AM (which lands at IST 2:30 PM) through UTC 9:00 PM (IST 2:30 AM). Across this +5h 30m gap, the middle of the UTC range usually lands in the IST afternoon — the reliable window for live calls between the two — while the early and late edges drift into IST morning or evening.
IST to UTC ranges from IST 9:00 AM (which lands at UTC 3:30 AM) through IST 9:00 PM (UTC 3:30 PM). Across this +5h 30m gap, the middle of the IST range usually lands in the UTC afternoon — the reliable window for live calls between the two — while the early and late edges drift into UTC morning or evening.
These direct answers are here for the exact-intent searches people actually use, like “10 AM UTC to IST” or “4 PM UTC in IST”.
8 AM UTC = 1:30 PM IST (13:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
9 AM UTC = 2:30 PM IST (14:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
10 AM UTC = 3:30 PM IST (15:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
11 AM UTC = 4:30 PM IST (16:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
12 PM UTC = 5:30 PM IST (17:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
1 PM UTC = 6:30 PM IST (18:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
2 PM UTC = 7:30 PM IST (19:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
3 PM UTC = 8:30 PM IST (20:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
4 PM UTC = 9:30 PM IST (21:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
5 PM UTC = 10:30 PM IST (22:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
6 PM UTC = 11:30 PM IST (23:30). On today's live calendar that lands on Thu, Nov 5 in IST, which means the answer is a same day conversion rather than a static offset lookup.
9 PM UTC = 2:30 AM IST (02:30). On today's live calendar that lands on Fri, Nov 6 in IST, which means the answer is a next day conversion rather than a static offset lookup.
The live gap is +5h 30m right now, based on Etc/UTC at +00:00 and Asia/Kolkata at +05:30. Neither reference zone shows an offset change in the next year, so the gap should stay stable.
The most usable workday block right now is about 2.5 hours: UTC 9:00 AM previous day to 11:30 AM previous day, which lines up with IST 2:30 PM previous day to 5:00 PM previous day.
Etc/UTC
UTC · +00:00
Asia/Kolkata
GMT+5:30 · +05:30
These are the busiest live references selected from the abbreviation families on this page.
| UTC | IST |
|---|---|
| 00:00 | 05:30 |
| 01:00 | 06:30 |
| 02:00 | 07:30 |
| 03:00 | 08:30 |
| 04:00 | 09:30 |
| 05:00 | 10:30 |
| 06:00 | 11:30 |
| 07:00 | 12:30 |
| 08:00 | 13:30 |
| 09:00 | 14:30 |
| 10:00 | 15:30 |
| 11:00 | 16:30 |
| 12:00 | 17:30 |
| 13:00 | 18:30 |
| 14:00 | 19:30 |
| 15:00 | 20:30 |
| 16:00 | 21:30 |
| 17:00 | 22:30 |
| 18:00 | 23:30 |
| 19:00 | 00:30 |
| 20:00 | 01:30 |
| 21:00 | 02:30 |
| 22:00 | 03:30 |
| 23:00 | 04:30 |
Countries represented here include No country breakdown available.
Countries represented here include India, Israel, and Sri Lanka.
Once a conversion pair matters, people usually need a city page, compare page, or a broader browse surface next.
Interactive converter
Move from this static pair into the full timezone converter with more cities and abbreviations.
Compare city pairs
Use compare pages when the practical question is overlap, not just offset arithmetic.
World clock
Open live city clocks after narrowing the timezone pair you care about.
Browse city pages
Jump into the strongest city pages when you want location-specific timezone context.
