A History of South African Standard Time

When the railways forced South Africa to pick a clock

A train passenger in the 1880s could step onto a platform in Cape Town, travel inland, and arrive to find the station clock disagreed with the local church clock by 20 minutes. Miss a connection and the next train might be hours away.

The Cape Government Railways and the Natal Government Railways each built their own time systems. Because the Cape and Natal lines used different reference points, the solution was partial. By the 1890s, the Cape Colony ran on a time based on the 22.5°E meridian. The Transvaal and Orange Free State used 30°E. The difference: roughly 30 minutes.

Before the railways, nobody cared. Every town set its clocks by the sun. When it was noon in Cape Town, it was 11:37 in Durban and 11:23 in Johannesburg. Ox wagons do not run to a timetable.

The National Time Act and the birth of SAST

The Union of South Africa formed in 1910. Standardising time was one of the early administrative tasks. The result: the National Time Act, passed in 1923. It established South African Standard Time as UTC+2, based on the 30°E meridian.

Every province, every town, every railway line adopted SAST. The law was simple. One country, one clock. That decision has never been reversed. SAST remains UTC+2, governed by the same act, subsequently amended but never repealed.

Did Cape Town and Johannesburg once run on different clocks?

Before the 1923 Act, Cape Town ran on a time roughly 1 hour 14 minutes behind SAST. The interior, including Johannesburg and Pretoria, already used something close to UTC+2 because of the railway standard. So for a period in the early 1900s, South Africa effectively had two time zones. A telegram sent from Cape Town to Johannesburg would arrive at a different local hour than the sender expected. The National Time Act ended that confusion in one stroke.

South Africa's two failed daylight saving experiments

South Africa tried daylight saving time twice. Both times it failed.

The first experiment ran from 1942 to 1944, during World War II. Clocks moved forward by one hour to UTC+3 to save fuel and extend productive daylight. The experiment ended with the war. Public opinion was mixed. The agricultural sector complained that morning light was lost.

The second experiment came in the 1970s. The exact years are 1973 to 1974. Clocks advanced to UTC+3 again. This time the opposition was louder. Farmers said livestock routines were disrupted. The mining industry argued that underground shift changes were harder to manage. The public disliked dark winter mornings. After two years, the government repealed the change.

No DST has been attempted since.

Who killed daylight saving in South Africa

The two DST experiments failed for the same reasons.

Agriculture: South Africa's farming sector operates on daylight, not clock time. Moving the clock forward meant cows were milked in darkness and crops were harvested in morning gloom. Farmers lobbied hard against both trials.

Mining: the industry, a powerful economic force, argued that shift changes and safety protocols could not easily adapt to a shifted clock. Underground workers started their day in darkness.

Public opinion: South Africans voted with their complaints. The 1970s experiment generated so much negative feedback that no political party has proposed reintroducing DST since.

The IANA time zone database and Africa/Johannesburg

The IANA time zone database, which powers every smartphone, computer and server, records South Africa's time zone as Africa/Johannesburg. This single zone covers the entire country: Durban, Cape Town, Pretoria, every other city.

There is no Africa/Durban or Africa/Cape_Town entry. Searching for one will cause your device to default to Africa/Johannesburg. The database lists SAST as UTC+2, no DST, with a history that records the two experimental periods.

Why does a country spanning 14 degrees of longitude use one zone?

South Africa stretches from roughly 16.5°E near Alexander Bay to 32.9°E near the Mozambique border. That is enough width for two standard time zones. The sun rises nearly an hour later in the west than in the east.

Yet the country uses one zone. The reason is practical: a single time zone simplifies business, transport, broadcasting and government. The inconvenience is minor. On the June solstice, sunrise in Durban is 06:50. On the December solstice, it is 04:51. Both Cape Town and Durban use the same clock. Residents adjust their daily schedules instead.

SAST and its neighbours: who shares the same offset

SAST is UTC+2, the same offset as Central Africa Time (CAT). These countries share SAST year-round:

East Africa Time (EAT), used by Kenya, Uganda and Tanzania, is UTC+3, one hour ahead. West Africa Time (WAT), used by Nigeria and Ghana, is UTC+1, one hour behind. Namibia uses CAT (UTC+2) and observes DST, shifting to UTC+3 in summer. Check Namibia's current DST status before scheduling, as rules may change.

Practical takeaway: calling from Durban to Lusaka or Harare means identical time. Calling Nairobi means adding one hour. Calling Lagos means subtracting one hour.

How to schedule across South Africa's fixed offset

If you need a meeting between Durban and another city, do not guess the offset. The difference between Durban and London changes twice a year because the UK shifts clocks, not South Africa. In January, London is 2 hours behind Durban. In July, it is 1 hour behind.

The Durban Time Zone page lists the current offset and IANA details. The Daylight Saving in Durban page confirms that no clock change happens here.