Holidays in Bangladesh

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

About Time in Bangladesh

Dhaka Once Ran on 6:01:40, Then Borrowed a Meridian Farther West

The oldest part of Dhaka's digital time-zone record contains two offsets that reveal two different ideas about what a clock should represent. IANA reconstructs local mean time before 1890 as 6 hours, 1 minute and 40 seconds ahead of Greenwich. Converted back into longitude at fifteen degrees per hour, that corresponds to a meridian of 90 degrees 25 minutes east, essentially the longitude of Dhaka expressed as time.

From 1890, however, the database changes to +5:53:20 and labels the standard HMT. Even IANA does not present the expansion of that abbreviation as certain: its source file annotates it with the question "Howrah Mean Time?". The offset corresponds to 88 degrees 20 minutes east, well west of Dhaka. The eight-minute-twenty-second difference therefore represents more than clock adjustment. In the historical model, local astronomical time gave way to a standard associated with another meridian.

The sequence became much more abrupt during the Second World War. IANA places Dhaka at +6:30 from October 1941, at +5:30 from 15 May 1942, and back at +6:30 from September 1942. On 30 September 1951, when the territory was East Bengal within Pakistan, the modeled clock moved backward thirty minutes to +6:00. That final offset survived the creation of Bangladesh and remains the national civil offset today.

These early transitions need to be read with appropriate caution. IANA itself says that much of its Asian data through 1990 ultimately derives from Shanks and Pottenger, a compilation known to contain errors and lacking source citations. The sequence is indispensable for historical software, but it is not equivalent to a complete archive of contemporary Bengal and East Pakistan legislation. The uncertainty surrounding the very label HMT is a useful example of why historical time-zone data should be treated as reconstruction, not unquestionable fact.

For 195 Days in 2009, Bangladesh Lived at UTC+7

Bangladesh tried daylight saving only once, during a severe electricity shortage in 2009. Government figures for the beginning of that year put available generation well below national demand, and the Power Division proposed advancing the clock so that offices, shops and households would use more evening daylight. The cabinet approved the experiment in June.

The transition was unusually easy to misunderstand because it was scheduled around midnight. The final rule, confirmed to IANA from Bangladesh Telecommunication Regulatory Commission information, advanced clocks at 23:00 on 19 June. The next displayed time was 00:00 on 20 June. For the first time, Bangladesh was temporarily seven hours ahead of UTC rather than six.

The scheme was initially discussed as a seasonal measure, but its end date kept moving. By September the government had decided not to restore standard time on 1 October while it reconsidered the policy. Power Development Board figures reported at the time suggested that evening peak demand had fallen by as much as about 200 MW during parts of June and July, although the demand peak also shifted later into the night. The figures describe the observed electricity system, not a controlled experiment proving that every megawatt of the reduction was caused solely by the clock change.

The trial finally ended at the close of 31 December 2009. The government planned to advance the clock again in 2010, but the cabinet cancelled that plan in March, citing public difficulties, particularly those affecting schoolchildren. Bangladesh therefore has an unusually compact daylight-saving history: one continuous experiment, beginning in June and ending on New Year's Eve, followed by no recurrence.

The Country's Only DST Experiment Changed the Clock Time of a Total Eclipse

By coincidence, the months spent at UTC+7 included one of the century's major astronomical events. On 22 July 2009 the path of a total solar eclipse crossed northern Bangladesh. NASA's track continued from India and Nepal through Bangladesh, Bhutan, Myanmar and China before reaching the Pacific, where the global maximum totality approached six minutes forty seconds. Bangladesh was inside the path, but its local durations were shorter.

Panchagarh became one of the principal observing areas. Calculations for the district give roughly 3 minutes 59 seconds of totality, with maximum eclipse near 07:58 on the clock then in use. Contemporary reporting described large crowds gathering in the north and an organized observing programme involving the district administration and the Bangladesh Astronomical Society.

The local timestamp contains a historical trap. A modern conversion that blindly assumes Bangladesh was always UTC+6 would place the maximum about an hour earlier on the civil clock. In July 2009 the country was actually using UTC+7, so approximately 07:58 was the correct local legal time for the Panchagarh maximum. The eclipse is therefore a rare astronomical event whose historical timestamp directly depends on remembering Bangladesh's short-lived daylight-saving experiment.

The Bangla Calendar Was Rebuilt to Keep Historical Dates from Drifting

Bangladesh operates with more than one calendrical framework. The Gregorian calendar governs most international and administrative dating, while Bangabda remains deeply embedded in cultural life. Its history reflects an old practical problem: agricultural seasons follow the solar year, while a purely lunar fiscal calendar moves through the seasons. Banglapedia traces the development of the Bangla year to Mughal-era attempts to make revenue accounting better match the agricultural cycle.

Calendar arithmetic created a different problem in the twentieth century. Traditional month lengths did not produce a simple, predictable correspondence with Gregorian dates. A Bangla Academy reform effort under Muhammad Shahidullah sought to regularize the system, using fixed month lengths and a leap-year mechanism rather than allowing month lengths to depend entirely on older astronomical almanac calculations.

Another adjustment took effect in 2019. Under the revised Bangladeshi system, the first six months, from Baishakh through Ashwin, contain 31 days each. Kartik, Agrahayan, Poush, Magh and Chaitra contain 30 days, while Falgun has 29 days and receives a thirtieth day in a Gregorian leap year. Pahela Baishakh remains fixed on 14 April.

The reform was not simply a matter of tidying arithmetic. It was designed so that historically important dual-calendar dates would remain aligned: 21 February with 8 Falgun, 26 March with 12 Chaitra and 16 December with 1 Poush. Changing the length of Ashwin by one day was enough to move later dates through the rest of the Bangla year. It is a good example of calendar engineering in the literal sense: a system of months was deliberately redesigned so that two different chronological frameworks would continue to agree at selected points.

Precision Time Is Now a Laboratory Quantity at BSTI

Bangladesh's National Metrology Laboratory was established within the Bangladesh Standards and Testing Institution in 2010 with support from the government, UNIDO, the European Union and Norway. Its seven laboratory areas include an Electrical, Time and Frequency Measurement Laboratory. Six of the national metrology laboratories subsequently received joint accreditation from Norwegian Accreditation and the Bangladesh Accreditation Board in 2013.

This work belongs to a different level of timekeeping from deciding whether the public clock reads UTC+6 or UTC+7. Time and frequency metrology deals with measuring oscillators, calibration and traceability, where errors are evaluated far below the one-second scale. The historical progression is unusually broad: Dhaka's nineteenth-century clock could be described to the second as a longitude, twentieth-century governments shifted national time by thirty or sixty minutes, and the present metrology infrastructure works on maintaining reproducible measurements of the second itself.

Frequently Asked Questions