Explore · time zones
Kuala Lumpur to EET converter
Malaysia Time (Kuala Lumpur) → Eastern European Time (Helsinki)
Quick answer
The difference changes with daylight saving time. Helsinki is 6 hours behind Kuala Lumpur from Jan 1, 2026 to Mar 29, 2026 01:00 UTC (Helsinki on EET · UTC+2); 5 hours behind Kuala Lumpur from Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTC (Helsinki on EEST · UTC+3); 6 hours behind Kuala Lumpur from Oct 25, 2026 01:00 UTC to Dec 31, 2026 (Helsinki on EET · UTC+2).
- Jan 1, 2026 to Mar 29, 2026 01:00 UTCKuala Lumpur (UTC+8) → Helsinki (EET, UTC+2)Helsinki is 6 hours behind Kuala Lumpur
- Mar 29, 2026 01:00 UTC to Oct 25, 2026 01:00 UTCKuala Lumpur (UTC+8) → Helsinki (EEST, UTC+3)Helsinki is 5 hours behind Kuala Lumpur
- Oct 25, 2026 01:00 UTC to Dec 31, 2026Kuala Lumpur (UTC+8) → Helsinki (EET, UTC+2)Helsinki is 6 hours behind Kuala Lumpur
9:00 AM UTC+8 in Kuala Lumpur is 3:00 AM EET (UTC+2) in Helsinki, the same day. Helsinki is 6 h behind Kuala Lumpur.
| Format | Result | Copy |
|---|---|---|
| HelsinkiEET · UTC+2 · Wednesday, January 14, 2026 · the same day | 3: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768352400 | |
| RFC 2822UTC | Wed, |
Conversions use Kuala Lumpur (Asia/Kuala_Lumpur) and Helsinki (Europe/Helsinki). Other cities reached through search aliases may have different historical rules.
Current time in Kuala Lumpur and Helsinki
Hour by hour: Kuala Lumpur (UTC+8) → Helsinki (EET, UTC+2)
Both sides are inside 9:00–17:00 from 3:00 PM to 5:00 PM UTC+8 in Kuala Lumpur (2 hours).
| Kuala Lumpur | Helsinki | Day |
|---|---|---|
| 12:00 AM | 6:00 PM | previous day |
| 1:00 AM | 7:00 PM | previous day |
| 2:00 AM | 8:00 PM | previous day |
| 3:00 AM | 9:00 PM | previous day |
| 4:00 AM | 10:00 PM | previous day |
| 5:00 AM | 11:00 PM | previous day |
| 6:00 AM | 12:00 AM | same day |
| 7:00 AM | 1:00 AM | same day |
| 8:00 AM | 2:00 AM | same day |
| 9:00 AM | 3:00 AM | same day |
| 10:00 AM | 4:00 AM | same day |
| 11:00 AM | 5:00 AM | same day |
| 12:00 PM | 6:00 AM | same day |
| 1:00 PM | 7:00 AM | same day |
| 2:00 PM | 8:00 AM | same day |
| 3:00 PM | 9:00 AM | same day |
| 4:00 PM | 10:00 AM | same day |
| 5:00 PM | 11:00 AM | same day |
| 6:00 PM | 12:00 PM | same day |
| 7:00 PM | 1:00 PM | same day |
| 8:00 PM | 2:00 PM | same day |
| 9:00 PM | 3:00 PM | same day |
| 10:00 PM | 4:00 PM | same day |
| 11:00 PM | 5:00 PM | same day |
Hour by hour: Kuala Lumpur (UTC+8) → Helsinki (EEST, UTC+3)
Both sides are inside 9:00–17:00 from 2:00 PM to 5:00 PM UTC+8 in Kuala Lumpur (3 hours).
| Kuala Lumpur | Helsinki | Day |
|---|---|---|
| 12:00 AM | 7:00 PM | previous day |
| 1:00 AM | 8:00 PM | previous day |
| 2:00 AM | 9:00 PM | previous day |
| 3:00 AM | 10:00 PM | previous day |
| 4:00 AM | 11:00 PM | previous day |
| 5:00 AM | 12:00 AM | same day |
| 6:00 AM | 1:00 AM | same day |
| 7:00 AM | 2:00 AM | same day |
| 8:00 AM | 3:00 AM | same day |
| 9:00 AM | 4:00 AM | same day |
| 10:00 AM | 5:00 AM | same day |
| 11:00 AM | 6:00 AM | same day |
| 12:00 PM | 7:00 AM | same day |
| 1:00 PM | 8:00 AM | same day |
| 2:00 PM | 9:00 AM | same day |
| 3:00 PM | 10:00 AM | same day |
| 4:00 PM | 11:00 AM | same day |
| 5:00 PM | 12:00 PM | same day |
| 6:00 PM | 1:00 PM | same day |
| 7:00 PM | 2:00 PM | same day |
| 8:00 PM | 3:00 PM | same day |
| 9:00 PM | 4:00 PM | same day |
| 10:00 PM | 5:00 PM | same day |
| 11:00 PM | 6:00 PM | same day |
Worked examples
| When | Kuala Lumpur | Helsinki | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 10:00 PM UTC+8, January 14, 2026 | 4:00 PM EET (UTC+2), January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 10:00 PM UTC+8, July 15, 2026 | 5:00 PM EEST (UTC+3), July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 8:00 AM UTC+8, January 1, 2027 | 2:00 AM EET (UTC+2), 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.
Kuala Lumpur — Malaysia Time
- IANA identifier
- Asia/Kuala_Lumpur
- UTC offset
- UTC+8
- Daylight saving
- Not observed
- On this clock today
- Kuala Lumpur, Penang, Johor Bahru
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Asia/Kuala_Lumpur; a listed place's past or future rules may differ.
EET — Eastern European Time
- IANA identifier
- Europe/Helsinki
- Standard time
- EET · UTC+2
- Daylight time
- EEST · UTC+3
- On this clock today
- Helsinki, Bucharest, Kyiv, Sofia, Riga, Tallinn, Vilnius
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Europe/Helsinki; a listed place's past or future rules may differ.
Offset changes 2026–2027
- Mar 29, 2026, 4:00 AM local (2026-03-29 01:00 UTC): clocks go forward to UTC+3 (EEST)
- Oct 25, 2026, 3:00 AM local (2026-10-25 01:00 UTC): clocks go back to UTC+2 (EET)
- Mar 28, 2027, 4:00 AM local (2027-03-28 01:00 UTC): clocks go forward to UTC+3 (EEST)
- Oct 31, 2027, 3:00 AM local (2027-10-31 01:00 UTC): clocks go back to UTC+2 (EET)
EET is UTC+2; EEST (UTC+3) applies on the EU summer-time calendar. Athens and Cairo also use EET but are listed separately (Egypt follows its own daylight-saving dates).
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.