Planning dates run from Thu, Jan 1, 2026 through Mon, Dec 31, 2035. Future rules can be revised; review the data version when a distant schedule matters.
More context and planning advice
The European relationship changes around it
Johannesburg is UTC+02:00 on all four samples. It matches Berlin in July 2026 and is one hour ahead of Berlin on 27 October. If a weekly project meeting follows the Berlin clock, its Johannesburg time changes even though the Johannesburg row keeps the same UTC offset.
A dated view of the local clock
Four examples at 13:00 UTC, calculated with IANA 2026f. These are selected dates, not a live clock.
UTC date
UTC offset
Abbreviation
Local date and time
2026-01-15
UTC+02:00
SAST
Thu, 15 Jan 2026 · 15:00
2026-07-15
UTC+02:00
SAST
Wed, 15 Jul 2026 · 15:00
2026-10-27
UTC+02:00
SAST
Tue, 27 Oct 2026 · 15:00
2026-11-03
UTC+02:00
SAST
Tue, 3 Nov 2026 · 15:00
Use one table for the whole handoff
At 09:00 Johannesburg on 27 October, London reads 07:00 and Dubai reads 11:00. Moving the meeting to 11:00 Johannesburg brings London to 09:00 and Dubai to 13:00. Check each city’s full availability interval before assuming this illustrative combination fits your team.
Build a plan for this city
Select Johannesburg, add the other participants, and enter the actual meeting date. The planner uses Africa/Johannesburg; the abbreviation in the table is a display label. Adjust working days, hours, and meeting length before choosing a shared window. The supported planning range is 2026–2035.