What time is it in Kathmandu, Bagmati Province, Nepal

What time is it in Kathmandu

What time is it in Kathmandu is the wall hour in this city in the Kathmandu Valley, in Bagmati Province, the capital of Nepal. Nepal uses one legal offset. Pokhara, Biratnagar, and this city print the same numerals. They do not print the same ridge shadow, and they do not print the same sunrise minute. The IANA name is Asia/Kathmandu. Software borrowed the capital’s name for the whole country. It does not invent a municipal extra for the valley.

Nepal Time is a forty-five-minute offset. Whole-hour countries drop the forty-five minutes when they convert in their heads. India next door is a half-hour stamp. The usual miss is to treat Kathmandu as IST. It is not. UTC+5:45 is fifteen minutes ahead of India Standard Time. It is not UTC+5. It is not UTC+6. If your arithmetic landed on a round hour or on India’s half-hour, you converted a neighbour, not the valley. Redo it. Put the forty-five minutes back.

Kathmandu does not spring forward. Their March switch changes how far they sit from NPT. The valley does not switch. This city stays on UTC+5:45. Their last March note is a picture of their clocks, not of Bagmati Province.

A valley on a forty-five-minute stamp

UTC+5:45 is built on 86°15′E. Kathmandu sits a little west of that meridian, in the valley. The sun therefore peaks after 12:00 NPT. Office lunch and temple visiting hours are civil habits. The sun’s highest point over the valley floor is a later NPT minute. Guides who work by light and clerks who work by bells can both be right if they name which clock they meant.

The valley is geography. Hills around the valley can hide first light without moving the legal hour. That stretch is still one stamp. A gadget that shows two Kathmandu hours after a drive toward a surrounding ridge is wrong. Recalculate dawn when you leave the valley floor for a hillside town. Keep the hour.

Write NPT or UTC+5:45, never IST and never a rounded +5 or +6. Treat Delhi as fifteen minutes behind, not as “the same Himalayan hour.” Treat China as a different offset entirely, not as a neighbour you can guess.

Ignore daylight-saving footnotes that belong only to the other party. Write the city on the invite. “Nepal time” is the right offset and a sloppy place if someone is meeting you in Pokhara at dawn. The offset can stay. The sun table cannot be borrowed from another valley.

Monsoon light in a highland valley

Kathmandu’s year is a subtropical highland year with a wet monsoon and a drier stretch, cooler than a true tropical lowland because of the valley’s height. Hold that as climate, not as this hour’s sky. The sky line here is the valley’s present condition, not last year’s monsoon memory. A climate label will not tell you whether the courtyard is wet at 4 p.m. The live sky will.

Monsoon cloud can hide the disc after the listed sunrise. The sun table still reports the geometric event; cloud reports what you can see. Do not replace the calculated dawn with “the valley was still grey.” Both can be true. One is astronomy. The other is visibility. Winter mornings can be hazy. The valley’s summer evenings stretch because this latitude still has a real June, not because Nepal sprang forward. Do not reuse a monsoon dawn in the dry months and call the table still valid. Copying a Delhi pair is the wrong offset as well as the wrong pair.

India is fifteen minutes behind. That is not “close enough.” If you converted IST, you did not convert Kathmandu. Heat before the rains is ordinary here by valley standards. It still does not justify sliding a call because the courtyard feels later than the number. Print 16:45 NPT. Let the other party subtract; do not round the forty-five minutes away. Sensation is not UTC. After landing, set the phone to Nepal Time. The airport in the valley is not a buffer zone between India and China. It is Kathmandu, on this forty-five-minute stamp, as soon as you are on this city’s civil clock.