Why India and Nepal Have 30- and 45-Minute Offsets

Convert fractional time zones accurately, from India and Nepal to Adelaide, without rounding away the minutes.

Zone & Hour editorial · Published September 30, 2026 · Examples are explicitly dated

The world is not divided into whole-hour steps

The familiar drawing of twenty-four equal time zones is a teaching aid. Civil time zones are decisions made for real places, not a requirement that every clock differ from UTC by a whole number of hours. Some offsets contain thirty minutes; others contain forty-five.

India currently uses UTC+05:30 and Nepal uses UTC+05:45. Those extra minutes are part of the official clock relationship. They are not an approximation, an error in the converter or a reason to round to the nearest hour.

The fact that fifteen degrees of longitude corresponds roughly to an hour of solar time does not force governments to choose only whole-hour offsets. Geography, history and national standardization all affect civil clocks. Explaining a particular historical policy requires more than reading the current numeric offset; the tool therefore focuses on the rules needed to convert the selected date accurately.

India and Nepal are fifteen minutes apart

Mumbai and Kolkata both use India Standard Time. Kathmandu uses Nepal Time. Subtracting 05:30 from 05:45 gives a fifteen-minute difference, not an hour and not forty-five minutes.

These examples use the current fixed-offset relationship and are illustrated for October 5, 2026:

For a meeting starting at 9 AM in Mumbai, the Kathmandu participant sees 9:15 AM. Starting at 9 AM in Kathmandu produces 8:45 AM in Mumbai. The direction matters, just as it does with whole-hour differences.

Use the Kolkata to Kathmandu converter for a complete table and a different date. The city identifiers are Asia/Kolkata and Asia/Kathmandu.

Keep arithmetic in minutes

When calculating manually, convert the full offset to minutes. India’s offset is 330 minutes; Nepal’s is 345. Seoul’s is 540. Subtract source offset from destination offset, then apply that signed difference to the source time.

For 9 AM in Seoul, the Mumbai difference is 330 minus 540, or −210 minutes. Subtract three hours and thirty minutes to obtain 5:30 AM. For Kathmandu, the difference is −195 minutes, producing 5:45 AM.

Do not store India’s offset as the number 5.30 and treat it as decimal hours. Decimal 5.30 hours means five hours and eighteen minutes. A value of 5.5 hours represents five hours and thirty minutes, but integer minutes are usually clearer and avoid this class of misunderstanding.

Our converter calculates offsets in minutes and formats the hours and remainder separately. That also supports negative fractional offsets without accidentally giving the minute component the wrong sign.

Fractional offsets can also have daylight saving

Adelaide combines a half-hour base offset with a seasonal change. It is not enough to remember that “Adelaide is nine and a half hours ahead of UTC.” That describes only part of the year under its current schedule.

The half-hour component remains, while the seasonal change adjusts the hour component. Check the Adelaide clock or compare Sydney and Adelaide using the selected date. Do not apply Adelaide’s seasonal behavior to every Australian city that has a similar winter offset.

Grid boundaries are a design choice

A scheduling tool may offer quarter-hour increments because many common business meetings begin on :00, :15, :30 or :45. That grid is a convenience, not a rule of time zones. Someone can still request a meeting at 9:07, and the time picker accepts minutes.

In this site, the slider and recommendation search use fifteen-minute steps. The manual time input retains a specific minute, and the conversion itself does not round away a fractional offset. A meeting’s end is checked against each participant’s working interval, including intervals whose boundaries are not whole hours.

When sharing a schedule, preserve the minute digits even if most participants happen to see an on-the-hour time. Omitting them can turn “9:15 Kathmandu” into an incorrect “9 Kathmandu” assumption.

Historical offsets are a separate problem

Modern scheduling examples do not describe all past local clocks. Historical time-zone data may contain unusual offsets and changes. Browser support and the installed database determine which rules are available for a historical conversion.

For legal records, transport histories or archival research, verify the relevant local source and record the database version used. The IANA Time Zone Database and its explanatory theory notes describe the model and its historical limitations.

Frequently asked questions

Does a 45-minute offset mean Kathmandu is 45 minutes ahead of India?

No. Compare the entire offsets: UTC+05:45 minus UTC+05:30 is fifteen minutes.

Does every Indian city need a separate clock conversion?

For current civil-time scheduling, Mumbai and Kolkata share the same offset. Separate city names still help people recognize the participants’ locations and avoid ambiguity.

Why does my meeting begin on the half-hour in one city?

The difference between the two offsets has a fractional-hour component. Keep the resulting minutes and compare the full appointment in the meeting planner.