Cape town vs cat time

Cape Town and CAT are both UTC+2, but they are not the same

A meeting request lands in your inbox. Lusaka, 14:00. Your Cape Town calendar shows 14:00. You both join on time. The clocks match.

But the sender’s zone is Central Africa Time. Yours is South Africa Standard Time. Both sit at UTC+2. Both show the same wall-clock time. So why does the difference matter?

Time zones are not just offsets. They are rules about when that offset applies. CAT and SAST are identical today, but they are maintained by different authorities, have different histories, and could diverge if either region ever changes its rules.

What is CAT, exactly?

Central Africa Time is the zone used by Botswana, Burundi, the eastern Democratic Republic of the Congo, Malawi, Mozambique, Rwanda, South Sudan, Sudan, Zambia, and Zimbabwe. Like SAST, it sits at UTC+2. Unlike SAST, CAT is not a single country's standard. It is a regional label the IANA time zone database applies to a cluster of African countries that use UTC+2 year-round and do not observe daylight saving time.

The IANA identifiers for CAT are not one zone but many: Africa/Maputo, Africa/Blantyre, Africa/Lusaka, and others. Each is a separate entry in the database, even though they share the same offset and rules. The IANA database preserves local history and legal timekeeping for each territory.

What is SAST, and how is it different?

South Africa Standard Time is the legal time for the entire Republic of South Africa. Its IANA identifier is Africa/Johannesburg. It applies in Cape Town, Johannesburg, Durban, and every other city in the country.

SAST has been UTC+2 since 1 March 1903, when the Cape Colony adopted standard time. The only interruptions were two brief daylight saving experiments: the first during World War II (1942 to 1944) and a second trial from 1979 to 1980. Both were abolished. South Africa has not changed its clocks since 1980, and no serious proposal to reintroduce DST exists today.

CAT countries have their own histories. Zambia, for example, used UTC+1 before independence and shifted to UTC+2 in the 1960s. The rules differ, even if the current offset is the same.

Does the SAST vs CAT difference actually affect Cape Town schedules?

You will never miss a meeting because of CAT versus SAST. The wall clock is identical. But the difference bites in three scenarios.

1. Software and calendar systems. If your calendar app treats Africa/Johannesburg as "CAT" instead of "SAST", it is still correct for today. But if your system stores only the offset ("UTC+2") without the zone, a future rule change in either region will break your schedules. The IANA database knows that Africa/Johannesburg and Africa/Maputo are separate zones, even if they share the same offset right now. Always use the full IANA zone identifier (Africa/Johannesburg for Cape Town), never just the offset or the abbreviation.

2. Historical data. If you are looking up a Cape Town timestamp from 1943, SAST was not UTC+2. It was UTC+1 because of the wartime DST experiment. CAT countries had their own rules during that period. The IANA database tracks these differences. A generic "CAT" label would be wrong for Cape Town in 1943.

3. Future rule changes. No one expects SAST or CAT to change soon. But zone rules change with political decisions. If Zambia or Malawi ever adopted DST, CAT would shift seasonally while SAST stayed fixed. Your Cape Town calendar would still be correct. Any system that conflated the two zones would fail.

Can you just call Cape Town time "CAT" and move on?

The shortcut that works: for scheduling calls and meetings in 2026 and 2027, treat Cape Town and CAT cities as the same time. They are. Use UTC+2 as your mental model.

The shortcut that does not work: calling Cape Town's zone "CAT". It is not. South Africa's government maintains its own legal time standard through the National Metrology Institute of South Africa. The IANA database assigns Cape Town to Africa/Johannesburg, not to a CAT zone. Calling it CAT is technically incorrect, and it risks confusion if you are building software, publishing data, or writing documentation.

What about other UTC+2 zones that are not CAT?

You may hear people say Cape Town is on "EET" (Eastern European Time) or "CEST" (Central European Summer Time). Those are wrong too. EET is used by Finland, Greece, and other European countries that switch to EEST in summer. CEST is a daylight saving offset. Cape Town never switches. The correct name is SAST.

The only real neighbour is CAT. Same offset, different zone.

Who should treat SAST and CAT as separate?

Anyone who writes code, stores zone data, or publishes schedules for a global audience should treat them as separate zones. Use Africa/Johannesburg for Cape Town and Africa/Maputo for Maputo. Do not collapse them into "CAT" or "UTC+2" in your database.

For everyone else, the difference is academic. Call Cape Town at the same time you would call Lusaka or Lilongwe. The clocks agree.

But if you are a developer or a data publisher, do not take the shortcut. The IANA database distinguishes these zones for a reason. Respect the distinction.