Why Does Nepal Have a 45-Minute Time Zone Offset? How Kathmandu Chose UTC+5:45 Over India's UTC+5:30
Almost every country on Earth sets its national clock to a whole number of hours ahead of or behind Coordinated Universal Time (UTC), while a handful of major jurisdictions—including India (UTC+05:30), Sri Lanka (UTC+05:30), Iran (UTC+03:30), Myanmar (UTC+06:30), and South Australia (UTC+09:30)—split the hour into 30-minute increments. Yet if you cross the border from northern India into Nepal, or land at Tribhuvan International Airport in Kathmandu, your watch jumps forward by one of the rarest increments in global horology: 15 minutes, placing the entire country on Nepal Standard Time (NPT, UTC+05:45).
When you compare international meeting windows in Tempo, Nepal stands out as the only sovereign country on Earth that observes a 45-minute UTC offset—joined globally only by New Zealand’s Chatham Islands (Pacific/Chatham, UTC+12:45 standard / UTC+13:45 daylight) and Australia’s unofficial Central Western Time zone along the Eyre Highway at Eucla (Australia/Eucla, UTC+08:45).
The 4-Minutes-Per-Degree Solar Math Behind the 86°15′E Gaurishankar Meridian
Why did Nepal choose UTC+05:45 instead of keeping India’s UTC+05:30 or rounding up to Bangladesh’s UTC+06:00? The answer lies in exact solar longitude arithmetic:
- Kathmandu’s Pre-1920 Local Mean Time (
UTC+05:41:16): Because Earth rotates360°in 1,440 minutes (15°per hour, or 4 minutes per degree of longitude), Kathmandu’s Durbar Square at85°19′E(85.32°E) sits exactly85.32 × 4 = 341.27minutes ahead of Greenwich, or 5 hours, 41 minutes, and 16 seconds ahead of UTC. - The 1920–1985 Indian Standard Time Era (
UTC+05:30): In 1920, during the Rana dynasty, Nepal formally adopted Indian Standard Time (UTC+05:30, anchored to the82°30′Emeridian near Mirzapur in Uttar Pradesh) to simplify telegraph and railway schedules with British India. Because82.50°Elies nearly 3 degrees west of Kathmandu and 5.5 degrees west of eastern Nepal, Indian Standard Time left Nepalese solar noon occurring 11 to 22 minutes early on the wall clock. - The 1986 Shift to Mount Gaurishankar (
86°15′E = UTC+05:45): In 1986, King Birendra’s government established an independent national meridian passing through the summit of Gaurishankar (7,134 m / 23,406 ft), a sacred Himalayan peak in Dolakha District about 100 km east of Kathmandu at86°15′E(86.25°E). Multiplying86.25° × 4 minutes/degreeyields345.0 minutes = +5 hours and 45 minutes.
How South Asia’s Stepped Time Zones Compare Across 25 Degrees of Longitude
South Asia is the only region on the planet where traveling east-to-west crosses 00-minute, 30-minute, and 45-minute time zones within a few hundred kilometers. Comparing the five adjacent IANA zones shows how closely each meridian tracks true solar noon:
| Jurisdiction / City | IANA Time Zone | Reference Meridian (City Longitude) | True Solar Offset (Min) | Legal Civil Zone | Legal Offset (Min) | Solar Noon Clock Skew |
|---|---|---|---|---|---|---|
| Islamabad / Karachi, Pakistan | Asia/Karachi |
75.00°E (73.0°E) |
+292.0 min |
PKT (UTC+05:00) |
+300 min | +8.0 min |
| New Delhi / Mirzapur, India | Asia/Kolkata |
82.50°E (77.2°E) |
+330.0 min |
IST (UTC+05:30) |
+330 min | 0.0 min (@ 82.5°E) |
| Kathmandu, Nepal (1986–Present) | Asia/Kathmandu |
86.25°E (85.32°E) |
+341.3 min |
NPT (UTC+05:45) |
+345 min | +3.7 min (3m 44s) |
| Dhaka, Bangladesh | Asia/Dhaka |
90.00°E (90.41°E) |
+361.6 min |
BST (UTC+06:00) |
+360 min | -1.6 min |
| Yangon, Myanmar | Asia/Yangon |
97.50°E (96.20°E) |
+384.8 min |
MMT (UTC+06:30) |
+390 min | +5.2 min |
| Eucla, Australia (Eyre Hwy) | Australia/Eucla |
131.25°E (128.9°E) |
+515.6 min |
ACWST (UTC+08:45) |
+525 min | +9.4 min |
| Chatham Islands, New Zealand | Pacific/Chatham |
176.50°W |
+734.0 min |
CHAST (UTC+12:45) |
+765 min | +31.0 min |
“By anchoring Nepal Standard Time to the 86°15′E meridian of Mount Gaurishankar, Kathmandu sits within 3 minutes and 44 seconds of true astronomical solar noon—one of the tightest solar-to-civil clock alignments of any capital city on Earth.”
Three Practical Rules for Software Engineers and Travelers
- Never Store Time Zone Offsets as Integer Hours (or Half-Hours): Legacy scheduling databases that store UTC offsets as
INThours orDECIMAL(3,1)half-hours (+5.5) silently corrupt timestamps fromAsia/Kathmandu(+5.75hours =+345minutes),Australia/Eucla(+8.75hours =+525minutes), andPacific/Chatham(+12.75/+13.75hours). Always store offsets in integer minutes or seconds—or store UTC timestamps alongside the full IANA string (Asia/Kathmandu). - No Daylight Saving Time Transitions Since 1986: Nepal does not observe Daylight Saving Time, meaning its offset vs. India is a constant
+15 minutesyear-round (12:00 PMin New Delhi is always12:15 PMin Kathmandu) and its offset vs. Bhutan (Asia/Thimphu,UTC+06:00) and Bangladesh (Asia/Dhaka,UTC+06:00) is a constant-15 minutes. - Cross-Hemisphere Meeting Windows Flip by 60 Minutes Twice a Year: Because London, Berlin, and New York shift for Daylight Saving Time while Kathmandu stays fixed at
UTC+05:45, a9:00 AMEastern call in New York lands at6:45 PMin Kathmandu during U.S. Daylight Saving Time (EDT, UTC-4) but shifts to7:45 PMin Kathmandu during U.S. Standard Time (EST, UTC-5).
Coordinating calls across Kathmandu (UTC+05:45), New Delhi (UTC+05:30), Dhaka (UTC+06:00), London, and New York? Open Tempo in your browser to visualize 15-minute and 30-minute time-zone overlaps instantly, or explore our international time-zone guides.