India Time Zone Overlap Calculator — How Many Hours You Actually Share With a Remote Team in India
Pick your city and the shift you would ask for, and get the real number of live working hours you would share with an India-based team member. Including the combinations where the honest answer is zero.
India runs on one time zone all year: IST, UTC+05:30. No daylight saving, ever. So the gap between your desk and theirs moves twice a year because your clocks change, not because theirs do.
Work Out Your Own Overlap
Everything is computed in half-hour steps, because IST sits on a :30 offset and an hourly grid quietly rounds every answer.
The Full Overlap Matrix
Hours of live overlap against a 09:00–17:00 working day in your own time zone, standard time (no daylight saving). Every figure is computed, not estimated. Read the zeros as carefully as the fives.
| Your region | Standard day 09:00–18:00 IST |
Early start 06:30–15:30 IST |
Mid shift 12:30–21:30 IST |
Evening shift 14:00–23:00 IST |
Night shift 18:30–03:30 IST |
Deep night 20:30–05:30 IST |
|---|---|---|---|---|---|---|
| US Pacific Los Angeles, Seattle, San Francisco |
0 | 0 | 0 |
0.5 h
09:00–09:30 |
5 h
09:00–14:00 |
7 h
09:00–16:00 |
| US Mountain Denver, Phoenix (no DST) |
0 | 0 | 0 |
1.5 h
09:00–10:30 |
6 h
09:00–15:00 |
8 h
09:00–17:00 |
| US Central Chicago, Dallas, Austin |
0 | 0 |
1 h
09:00–10:00 |
2.5 h
09:00–11:30 |
7 h
09:00–16:00 |
8 h
09:00–17:00 |
| US Eastern New York, Toronto, Miami |
0 | 0 |
2 h
09:00–11:00 |
3.5 h
09:00–12:30 |
8 h
09:00–17:00 |
7 h
10:00–17:00 |
| UK & Ireland London, Dublin, Manchester |
3.5 h
09:00–12:30 |
1 h
09:00–10:00 |
7 h
09:00–16:00 |
8 h
09:00–17:00 |
4 h
13:00–17:00 |
2 h
15:00–17:00 |
| Central Europe Berlin, Paris, Amsterdam, Madrid |
4.5 h
09:00–13:30 |
2 h
09:00–11:00 |
8 h
09:00–17:00 |
7.5 h
09:30–17:00 |
3 h
14:00–17:00 |
1 h
16:00–17:00 |
| UAE Dubai, Abu Dhabi |
7.5 h
09:00–16:30 |
5 h
09:00–14:00 |
6 h
11:00–17:00 |
4.5 h
12:30–17:00 |
0 | 0 |
| Singapore & HK Singapore, Hong Kong |
5.5 h
11:30–17:00 |
8 h
09:00–17:00 |
2 h
15:00–17:00 |
0.5 h
16:30–17:00 |
0 | 0 |
| Australia West Perth |
5.5 h
11:30–17:00 |
8 h
09:00–17:00 |
2 h
15:00–17:00 |
0.5 h
16:30–17:00 |
0 | 0 |
| Australia East Sydney, Melbourne, Canberra |
3.5 h
13:30–17:00 |
6 h
11:00–17:00 |
0 | 0 | 0 |
1 h
09:00–10:00 |
| Australia (QLD) Brisbane, Gold Coast |
3.5 h
13:30–17:00 |
6 h
11:00–17:00 |
0 | 0 | 0 |
1 h
09:00–10:00 |
| New Zealand Auckland, Wellington |
1.5 h
15:30–17:00 |
4 h
13:00–17:00 |
0 | 0 |
1 h
09:00–10:00 |
3 h
09:00–12:00 |
Times shown under each figure are in your local clock. Where a region observes daylight saving, add or subtract an hour of overlap for roughly half the year — use the calculator above and tick the daylight saving box to see which way it moves for you.
What the Numbers Actually Mean
The row that surprises people is US Pacific. A standard Indian working day and a standard Californian working day do not touch at any point — 18:00 IST is 05:30 in Los Angeles. There is no clever scheduling that fixes that. Somebody has to move their day, and the only real question is who, by how much, and whether they agreed to it.
The UK row is the opposite story. A plain 09:00–18:00 IST day already lands three and a half hours inside a London working day without anyone doing anything unusual, and Central Europe gets four and a half. Ask for a mid or evening shift instead and both jump to seven or eight — a nearly complete shared day, bought with a start time that is still perfectly civil in India. That is why offshore hiring tends to be a much shorter conversation in London or Berlin than in San Francisco.
Australia is the row most people read backwards. The instinct is to ask for a later Indian shift; the maths says the opposite. Sydney and Melbourne get six hours against an early 06:30 IST start and exactly zero against a mid or evening shift, because by the time an Indian afternoon begins the Australian day is over. Perth does best of all — eight full hours on that same early start — since the gap is only two and a half. If you are in Australia, most of the objections written for an American audience simply do not apply to you, but the shift you should be asking for is not the one the American articles recommend.
How much overlap is enough?
Two to three hours covers what most teams need to run: a standup, a demo, and one conversation to unblock whatever is stuck. It is not generous, but it works, and it works better than four hours of overlap that nobody protects in their calendar.
Below two hours you are running an asynchronous team whether you intended to or not. That is a legitimate way to work, but it needs different habits: decisions written down rather than spoken, handovers at the end of each side's day, and a tolerance for a question taking a full day to round-trip. Teams that fail at this usually fail because they kept the synchronous habits and just did them slowly.
Some roles do not tolerate a small overlap at all. Live phone support has to sit inside your customers' day, not yours. A single on-call engineer covering production needs to be awake when production is. For those, the shift is dictated by the work and the honest thing to do is price a night shift rather than pretend a mid shift covers it.
What a shifted day costs, and who pays it
Every overlap hour on the US rows of that table is manufactured. Somebody in India is starting at 18:30 or 20:30 and finishing after their family is asleep. That is a real cost, and it belongs in the conversation rather than buried in a rate.
In practice the arrangement that lasts is a partial shift. An evening or mid shift buys two to four live hours, the rest of the day runs asynchronously, and nobody is permanently nocturnal. Where a genuine night shift is unavoidable, rotation beats a permanent assignment, and it should be a role someone chose rather than one they inherited. Retention on permanent night work is the thing that breaks first, and it breaks quietly — usually about five months in.
Making three hours behave like six
The teams that get the most out of a narrow window treat it as expensive. Nothing goes into the shared hours that could have been written down. Status is read before the call, not delivered on it. The window is used for decisions, ambiguity and anything with a disagreement in it — the things that genuinely cost less face to face.
The second habit is a real handover. Whoever finishes their day last writes what moved, what is blocked and what they need an answer to before their next start. It takes ten minutes and it is the difference between losing one day to a blocked question and losing three.
If you want the version of this that is specific to your roles and your hours, how our engagements are set up covers shift agreement and handover in more detail, and the guide to managing a team across time zones goes into the working practices.
Time Zone Overlap FAQs
No. India has used a single time zone, IST (UTC+05:30), all year since 1947 — there is no summer or winter clock change. That means the gap between your office and an India-based team member changes twice a year because YOUR clocks move, not theirs. A US Eastern team gains an hour of morning overlap in winter and loses it in March; plan the shift around the smaller of the two numbers, not the larger.
For most delivery work, two to three hours is enough — long enough for a standup, a demo and one unblocking conversation. Below two hours you are running a genuinely asynchronous team and need the written habits to match. Roles that are interrupt-driven by nature, such as live phone support or a solo on-call engineer, need to be shifted to sit inside your day rather than merely to touch it.
Because 18:00 IST is 08:30 US Eastern and 05:30 US Pacific. The Indian working day has finished before the American one starts. Every US row on the matrix reads 0 for the standard, early and mid shifts. Any overlap you are quoted on a standard day shift is either rounding, an assumption about your team starting at 07:00, or wishful thinking. To get live hours with the US someone has to move: a night shift gives US Eastern a full eight hours, and US Pacific needs the deep-night pattern to reach seven.
It is a real cost and it should be priced and consented to, not assumed. Night-shift work is associated with measurable health and retention costs, and the honest version of this trade is that you are buying overlap with somebody else's sleep. In practice the workable version is a partial shift — an evening or mid shift that gives you two to four live hours — with the rest of the day run asynchronously, and rotation rather than permanent nights where a full night shift genuinely is required.
A standard 09:00–18:00 IST day gives the UK three and a half live hours and Central Europe four and a half, without asking anyone to work unsocial hours at all. Move to a mid shift (12:30–21:30 IST) and Central Europe reaches a full eight; an evening shift (14:00–23:00 IST) gives the UK the same. That is the single biggest practical advantage the UK and EU have over the US here — a nearly complete shared day costs an Indian start time of lunchtime, not midnight.
Yes, and for teams above about four people it is usually the right answer. A common shape is most of the team on a mid shift for the bulk of the work, with one or two people on an evening shift to carry the live conversation with you. It keeps the unsocial hours contained to the people who opted into them instead of spreading them across everyone.
Know Your Number? Let's Staff Around It.
Tell us the hours you need covered and we will come back with a shift pattern and a shortlist in 48 hours — including the honest version of what it asks of the person taking it.