Explore · time zones
Vladivostok to Lisbon converter
Vladivostok Time (Vladivostok) → Western European Time (Lisbon)
Quick answer
The difference changes with daylight saving time. Lisbon is 10 hours behind Vladivostok from Jan 1, 2026 to Mar 29, 2026 01:00 UTC (Lisbon on WET · UTC+0); 9 hours behind Vladivostok from Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTC (Lisbon on WEST · UTC+1); 10 hours behind Vladivostok 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 UTCVladivostok (UTC+10) → Lisbon (WET, UTC+0)Lisbon is 10 hours behind Vladivostok
- Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTCVladivostok (UTC+10) → Lisbon (WEST, UTC+1)Lisbon is 9 hours behind Vladivostok
- Oct 25, 2026 01:00 UTC to Dec 31, 2026Vladivostok (UTC+10) → Lisbon (WET, UTC+0)Lisbon is 10 hours behind Vladivostok
9:00 AM UTC+10 in Vladivostok is 11:00 PM WET (UTC+0) in Lisbon, the previous day. Lisbon is 10 h behind Vladivostok.
| Format | Result | Copy |
|---|---|---|
| LisbonWET · UTC+0 · Tuesday, January 13, 2026 · the previous day | 11: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768345200 | |
| RFC 2822UTC | T |
Conversions use Vladivostok (Asia/Vladivostok) and Lisbon (Europe/Lisbon). Other cities reached through search aliases may have different historical rules.
Current time in Vladivostok and Lisbon
Hour by hour: Vladivostok (UTC+10) → Lisbon (WET, UTC+0)
There is no time when both Vladivostok and Lisbon are inside 9:00–17:00.
| Vladivostok | Lisbon | Day |
|---|---|---|
| 12:00 AM | 2:00 PM | previous day |
| 1:00 AM | 3:00 PM | previous day |
| 2:00 AM | 4:00 PM | previous day |
| 3:00 AM | 5:00 PM | previous day |
| 4:00 AM | 6:00 PM | previous day |
| 5:00 AM | 7:00 PM | previous day |
| 6:00 AM | 8:00 PM | previous day |
| 7:00 AM | 9:00 PM | previous day |
| 8:00 AM | 10:00 PM | previous day |
| 9:00 AM | 11:00 PM | previous day |
| 10:00 AM | 12:00 AM | same day |
| 11:00 AM | 1:00 AM | same day |
| 12:00 PM | 2:00 AM | same day |
| 1:00 PM | 3:00 AM | same day |
| 2:00 PM | 4:00 AM | same day |
| 3:00 PM | 5:00 AM | same day |
| 4:00 PM | 6:00 AM | same day |
| 5:00 PM | 7:00 AM | same day |
| 6:00 PM | 8:00 AM | same day |
| 7:00 PM | 9:00 AM | same day |
| 8:00 PM | 10:00 AM | same day |
| 9:00 PM | 11:00 AM | same day |
| 10:00 PM | 12:00 PM | same day |
| 11:00 PM | 1:00 PM | same day |
Hour by hour: Vladivostok (UTC+10) → Lisbon (WEST, UTC+1)
There is no time when both Vladivostok and Lisbon are inside 9:00–17:00.
| Vladivostok | Lisbon | Day |
|---|---|---|
| 12:00 AM | 3:00 PM | previous day |
| 1:00 AM | 4:00 PM | previous day |
| 2:00 AM | 5:00 PM | previous day |
| 3:00 AM | 6:00 PM | previous day |
| 4:00 AM | 7:00 PM | previous day |
| 5:00 AM | 8:00 PM | previous day |
| 6:00 AM | 9:00 PM | previous day |
| 7:00 AM | 10:00 PM | previous day |
| 8:00 AM | 11:00 PM | previous day |
| 9:00 AM | 12:00 AM | same day |
| 10:00 AM | 1:00 AM | same day |
| 11:00 AM | 2:00 AM | same day |
| 12:00 PM | 3:00 AM | same day |
| 1:00 PM | 4:00 AM | same day |
| 2:00 PM | 5:00 AM | same day |
| 3:00 PM | 6:00 AM | same day |
| 4:00 PM | 7:00 AM | same day |
| 5:00 PM | 8:00 AM | same day |
| 6:00 PM | 9:00 AM | same day |
| 7:00 PM | 10:00 AM | same day |
| 8:00 PM | 11:00 AM | same day |
| 9:00 PM | 12:00 PM | same day |
| 10:00 PM | 1:00 PM | same day |
| 11:00 PM | 2:00 PM | same day |
Worked examples
| When | Vladivostok | Lisbon | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 12:00 AM UTC+10, January 15, 2026 | 2:00 PM WET (UTC+0), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 12:00 AM UTC+10, July 16, 2026 | 3:00 PM WEST (UTC+1), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 10:00 AM UTC+10, 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.
Vladivostok — Vladivostok Time
- IANA identifier
- Asia/Vladivostok
- UTC offset
- UTC+10
- Daylight saving
- Not observed
- On this clock today
- Vladivostok, Khabarovsk
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Asia/Vladivostok; a listed place's past or future rules may differ.
UTC+10 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.