Explore · time zones
SAST to Lisbon converter
South Africa Standard Time (Johannesburg) → Western European Time (Lisbon)
Quick answer
The difference changes with daylight saving time. Lisbon is 2 hours behind Johannesburg from Jan 1, 2026 to Mar 29, 2026 01:00 UTC (Lisbon on WET · UTC+0); 1 hour behind Johannesburg from Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTC (Lisbon on WEST · UTC+1); 2 hours behind Johannesburg from Oct 25, 2026 01:00 UTC to Dec 31, 2026 (Lisbon on WET · UTC+0).
- Jan 1, 2026 to Mar 29, 2026 01:00 UTCJohannesburg (SAST, UTC+2) → Lisbon (WET, UTC+0)Lisbon is 2 hours behind Johannesburg
- Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTCJohannesburg (SAST, UTC+2) → Lisbon (WEST, UTC+1)Lisbon is 1 hour behind Johannesburg
- Oct 25, 2026 01:00 UTC to Dec 31, 2026Johannesburg (SAST, UTC+2) → Lisbon (WET, UTC+0)Lisbon is 2 hours behind Johannesburg
9:00 AM SAST (UTC+2) in Johannesburg is 7:00 AM WET (UTC+0) in Lisbon, the same day. Lisbon is 2 h behind Johannesburg.
| Format | Result | Copy |
|---|---|---|
| LisbonWET · UTC+0 · Wednesday, January 14, 2026 · the same day | 7: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768374000 | |
| RFC 2822UTC | Wed, |
Conversions use Johannesburg (Africa/Johannesburg) and Lisbon (Europe/Lisbon). Other cities reached through search aliases may have different historical rules.
Current time in Johannesburg and Lisbon
Hour by hour: Johannesburg (SAST, UTC+2) → Lisbon (WET, UTC+0)
Both sides are inside 9:00–17:00 from 11:00 AM to 5:00 PM SAST (UTC+2) in Johannesburg (6 hours).
| Johannesburg | Lisbon | Day |
|---|---|---|
| 12:00 AM | 10:00 PM | previous day |
| 1:00 AM | 11:00 PM | previous day |
| 2:00 AM | 12:00 AM | same day |
| 3:00 AM | 1:00 AM | same day |
| 4:00 AM | 2:00 AM | same day |
| 5:00 AM | 3:00 AM | same day |
| 6:00 AM | 4:00 AM | same day |
| 7:00 AM | 5:00 AM | same day |
| 8:00 AM | 6:00 AM | same day |
| 9:00 AM | 7:00 AM | same day |
| 10:00 AM | 8:00 AM | same day |
| 11:00 AM | 9:00 AM | same day |
| 12:00 PM | 10:00 AM | same day |
| 1:00 PM | 11:00 AM | same day |
| 2:00 PM | 12:00 PM | same day |
| 3:00 PM | 1:00 PM | same day |
| 4:00 PM | 2:00 PM | same day |
| 5:00 PM | 3:00 PM | same day |
| 6:00 PM | 4:00 PM | same day |
| 7:00 PM | 5:00 PM | same day |
| 8:00 PM | 6:00 PM | same day |
| 9:00 PM | 7:00 PM | same day |
| 10:00 PM | 8:00 PM | same day |
| 11:00 PM | 9:00 PM | same day |
Hour by hour: Johannesburg (SAST, UTC+2) → Lisbon (WEST, UTC+1)
Both sides are inside 9:00–17:00 from 10:00 AM to 5:00 PM SAST (UTC+2) in Johannesburg (7 hours).
| Johannesburg | Lisbon | Day |
|---|---|---|
| 12:00 AM | 11:00 PM | previous day |
| 1:00 AM | 12:00 AM | same day |
| 2:00 AM | 1:00 AM | same day |
| 3:00 AM | 2:00 AM | same day |
| 4:00 AM | 3:00 AM | same day |
| 5:00 AM | 4:00 AM | same day |
| 6:00 AM | 5:00 AM | same day |
| 7:00 AM | 6:00 AM | same day |
| 8:00 AM | 7:00 AM | same day |
| 9:00 AM | 8:00 AM | same day |
| 10:00 AM | 9:00 AM | same day |
| 11:00 AM | 10:00 AM | same day |
| 12:00 PM | 11:00 AM | same day |
| 1:00 PM | 12:00 PM | same day |
| 2:00 PM | 1:00 PM | same day |
| 3:00 PM | 2:00 PM | same day |
| 4:00 PM | 3:00 PM | same day |
| 5:00 PM | 4:00 PM | same day |
| 6:00 PM | 5:00 PM | same day |
| 7:00 PM | 6:00 PM | same day |
| 8:00 PM | 7:00 PM | same day |
| 9:00 PM | 8:00 PM | same day |
| 10:00 PM | 9:00 PM | same day |
| 11:00 PM | 10:00 PM | same day |
Worked examples
| When | Johannesburg | Lisbon | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 4:00 PM SAST (UTC+2), January 14, 2026 | 2:00 PM WET (UTC+0), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 4:00 PM SAST (UTC+2), July 15, 2026 | 3:00 PM WEST (UTC+1), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 2:00 AM SAST (UTC+2), January 1, 2027 | 12:00 AM WET (UTC+0), January 1, 2027 | 2027-01-01T00:00:00.000Z | 1798761600 |
The ISO 8601 and Unix columns are the same instant written without a zone — how APIs and databases should store it. Need this for a whole column? Convert a CSV file.
SAST — South Africa Standard Time
- IANA identifier
- Africa/Johannesburg
- UTC offset
- SAST · UTC+2
- Daylight saving
- Not observed
- On this clock today
- Johannesburg, Cape Town, Pretoria, Durban
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Africa/Johannesburg; a listed place's past or future rules may differ.
UTC+2 all year.
Lisbon — Western European Time
- IANA identifier
- Europe/Lisbon
- Standard time
- WET · UTC+0
- Daylight time
- WEST · UTC+1
- On this clock today
- Lisbon, Porto, Madeira, Canary Islands
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Europe/Lisbon; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 29, 2026, 2:00 AM local (2026-03-29 01:00 UTC): clocks go forward to UTC+1 (WEST)
- Oct 25, 2026, 1:00 AM local (2026-10-25 01:00 UTC): clocks go back to UTC+0 (WET)
- Mar 28, 2027, 2:00 AM local (2027-03-28 01:00 UTC): clocks go forward to UTC+1 (WEST)
- Oct 31, 2027, 1:00 AM local (2027-10-31 01:00 UTC): clocks go back to UTC+0 (WET)
Mainland Portugal and Madeira keep the same clock as the UK (UTC+0 in winter, UTC+1 in summer). The Azores are one hour behind and are not on this clock.
Related conversions
File workspace
Converting a whole column of timestamps?
The free converter handles one value at a time across 82 formats and 92 zones. The file workspace converts an entire CSV column between any two formats and zones, previews the first rows, and leaves unreadable cells exactly as they were.
Offsets and change dates on this page are computed from IANA time zone database 2026f for 2026–2027; the live tool uses the same data.