GMT+4:30 Time Zone Countries list - UTC+4:30 Time Now

UTC+4:30 time now

Add four hours and thirty minutes to UTC. If UTC shows 06:00, Kabul shows 10:30. The half hour is deliberate — it places Afghanistan between the Gulf and Pakistan rather than aligning it with either.

Where UTC+4:30 applies

A single country, undivided: Afghanistan — the whole territory on one offset, known as Afghanistan Time. Kabul — the capital. Kandahar, Herat, Mazar-i-Sharif, Jalalabad, Kunduz — all on the same clock, from the western border to the eastern.

Iran previously used UTC+4:30 as its summer position, which is why older references sometimes list two countries here. Iran no longer changes its clocks, so today the offset is Afghanistan's alone.

Daylight saving and the fixed clock

Afghanistan does not observe daylight saving and has no history of doing so in its current time zone arrangement. The clock reads the same relationship to UTC in January as in July. What moves instead is the working calendar. The weekend and the pattern of the working week differ from the Monday-to-Friday assumption built into a lot of scheduling software, and the observance of Ramadan shifts business hours substantially without touching the clock. If you are coordinating with Kabul, the offset is the easy half of the problem.

Afghanistan sits half an hour off its neighbours in both directions — a country that declined to round in either direction, and has stuck to it.

The half-hour band across South Asia

UTC+4:30 belongs to a run of non-whole-hour offsets stretching east, and seeing them together explains why the region is a persistent source of conversion bugs. UTC+3:30 — Iran, thirty minutes behind Kabul.

UTC+4:30 — Afghanistan. UTC+5 — Pakistan, thirty minutes ahead. The border between Afghanistan and Pakistan is a half-hour step, not a whole one. UTC+5:30 — India and Sri Lanka. UTC+5:45 — Nepal, the only quarter-hour offset in regular civil use.

Crossing that whole band from Tehran to Kathmandu involves two and a quarter hours of change and not a single whole-hour boundary along the way.

Handling the offset in software

The same advice applies here as to every non-integer offset, and it is worth stating plainly: Store an instant in UTC alongside the IANA identifier Asia/Kabul, never a bare offset. Do not use an integer field for hours — it cannot represent this zone.

Test any conversion code against a half-hour zone specifically; whole-hour tests pass on broken arithmetic. Display the offset with minutes, as +04:30, so that a reader cannot mistake it for +04.