Holidays in Uzbekistan

Official national public holidays. Regional and religious observances may vary by area.

About Time in Uzbekistan

Uzbekistan's Historical Record Cannot Be Reduced to Tashkent Time

IANA's current time-zone data preserves two separate historical records for the territory of modern Uzbekistan: Asia/Tashkent and Asia/Samarkand. The distinction is not decorative. Their standard offsets differed for substantial parts of the twentieth century, so historical civil time in western Uzbekistan cannot safely be reconstructed from Tashkent alone.

The database places Tashkent on UTC+5 from May 2, 1924, and on UTC+6 from June 21, 1930. Samarkand follows a different sequence: UTC+4 from May 2, 1924, then UTC+5 from June 21, 1930. These dates are part of the tzdb historical reconstruction and should be treated as database history rather than proof that every clock across the territory changed simultaneously under one locally documented Uzbek law.

The one-hour separation continued into the period that matters most for computerized historical timestamps. A local time such as 10:00 could therefore represent different UTC instants depending on whether the event belonged to the Tashkent or Samarkand historical regime.

Samarkand's October 1981 Transition Changed the Time Regime Without Changing the Displayed Time

The Samarkand record contains a particularly unusual transition in 1981. On April 1, its UTC+5 standard time acquired a one-hour seasonal adjustment, producing an effective civil offset of UTC+6.

On October 1, the seasonal hour disappeared, but the underlying standard offset changed at the same boundary from UTC+5 to UTC+6. Immediately before the transition the effective offset was UTC+6 because of the one-hour seasonal adjustment. Immediately afterward it was still UTC+6, now as standard time.

No one-hour rollback was therefore required in the reconstructed Samarkand clock sequence at that boundary. What changed was the legal or administrative basis represented by the database: UTC+5 plus one seasonal hour became UTC+6 with no seasonal addition. It is a case where a time-zone transition exists in the historical data even though the wall-clock reading does not jump.

The arrangement was temporary. The next stage of the Samarkand record began in April 1982, when the underlying standard offset returned to UTC+5 and the seasonal rules were again applied. The sequence is one reason the western Uzbek record needs to remain separate from Tashkent.

For Early Local Time, the Seconds in tzdb Are Reconstructions, Not National Clock Laws

Before standardized offsets appear in the database, tzdb assigns Samarkand a local mean time of UTC+4:27:53 and Tashkent UTC+4:37:11. The Tashkent figure is based on a historical longitude-derived value reported by John Milne, while the Samarkand-side value comes from historical material used in the database's reconstruction.

Those second-level offsets should not be read as evidence that all clocks in either city, much less across the territory of modern Uzbekistan, were legally synchronized to those exact values. Local mean time is reconstructed for representative locations, and the database itself distinguishes this kind of historical material from later standardized civil offsets.

The difference between the two reconstructed local times is 9 minutes 18 seconds. That contrast helps explain why a single pre-standard national time cannot simply be projected backward over the whole country: longitude-based local time was inherently tied to place.

The Two Historical Records Eventually Converge on UTC+5

Official Uzbekistan government information now identifies the country's time zone as UTC+5. Government portals use the same offset for Tashkent time, and the current IANA records for both Asia/Tashkent and Asia/Samarkand also resolve to UTC+5 without a seasonal clock change.

The important historical detail is therefore not merely the present offset, but how two different regional clock histories arrived at the same national time. Tashkent and Samarkand no longer differ on the clock, while their separate database records remain necessary for interpreting older timestamps.

Frequently Asked Questions