Set a world clock to Kathmandu and you get a number that looks like a typo: UTC+5:45. Nepal time is offset from the global baseline not by whole hours, not even by a half hour, but by five hours and forty-five minutes. Only a few places on Earth use a 45-minute offset — Nepal, and the Chatham Islands of New Zealand are the notable ones. The odd number is not an accident. It is a small statement of geography and independence, and it has survived every attempt at rounding.
Where the 45 minutes comes from
Time zones follow the sun in theory. Local noon — the sun at its highest — moves west by one hour for every 15 degrees of longitude. Nepal's reference meridian runs at 86.25 degrees east, close to the longitude of Gaurishankar, a Himalayan peak east of Kathmandu. Divide 86.25 by 15 and you get 5.75 hours: five hours and forty-five minutes. Nepal simply took its true solar time and kept it, rather than rounding to a neighbor's clock.
The choice became official in 1986. Before that, Nepal ran on UTC+5:30, matching India's meridian. Moving fifteen minutes ahead aligned the clock with Nepal's own geography, and it drew a line that was as much political as astronomical. A country that was never colonized keeps its own time — literally.
The India question
The practical consequence people notice first: Nepal time is always fifteen minutes ahead of India. Cross the border at Birgunj or Bhairahawa and your phone jumps a quarter hour. The gap is small enough to forget and large enough to miss a train over, and generations of border-town travelers have learned to double-check which clock a departure board is using. The fifteen-minute difference has also become a quiet badge of identity, a way of saying the two countries run close but not identical.
No daylight saving, ever
Nepal has never used daylight saving time. The clock stays at UTC+5:45 all year. This makes conversions stable in one direction and confusing in the other: the gap between Nepal and London is 5:45 in winter but 4:45 in British summer, and the gap to New York swings between 10:45 and 9:45. When a call time with someone abroad feels off by an hour, their daylight saving shift is almost always the culprit — Nepal's clock did not move; theirs did.
Quick conversions worth memorizing
A few anchors cover most needs. India: subtract 15 minutes from Nepal time. Bangladesh: subtract 15 minutes... no — Bangladesh runs UTC+6, so add 15 minutes to Nepal time to get Dhaka. The Gulf (Dubai, Qatar): Nepal is 1:45 ahead of Dubai. London: 5:45 ahead in winter, 4:45 in summer. New York: 10:45 ahead in winter, 9:45 in summer. Sydney: Nepal is 5:15 behind in the Australian summer. For anything else, a converter beats arithmetic — and remember the direction: Nepal time is ahead of every one of its major diaspora destinations except Australia and East Asia.
Nepal time and the Nepali calendar
The 45-minute offset pairs with a calendar that is also its own thing. Nepal's official calendar is Bikram Sambat, which runs 56–57 years ahead of the Gregorian year, and the day's panchang — tithi, nakshatra and the rest — is computed for Nepali local time, not for UTC or Indian time. That matters for festivals: a tithi that changes at 6:10 in the morning Nepal time can put a festival on different days in Kathmandu and Delhi. Our daily panchang is calculated for Nepal, and the BS–AD converter handles the calendar side of the same puzzle.
The short version
Nepal time is UTC+5:45 because that is Nepal's actual solar time at its reference meridian, adopted officially in 1986. It never shifts for daylight saving. It sits 15 minutes ahead of India, and the odd offset is kept deliberately — a small daily reminder, on every clock in the country, that Nepal sets its own terms. If you remember one thing for scheduling: when a foreign contact's clocks change in spring or autumn, your gap with them changes too, even though Nepal never touched its clock.