Valletta time zone — UTC+02:00 right now (CEST)
Valletta, Malta, is currently on CEST (UTC+02:00) — 2 hours ahead of UTC. Use Europe/Malta in code, never the abbreviation and never a hard-coded offset.
Valletta · Europe/Malta
09:43:57
vs
Coordinated Universal Time · UTC
07:43:57
The identifier to put in your code
IANA time zone identifier
Europe/Malta
CEST is a label, not an identifier. Abbreviations are unregistered, they collide across regions, and no date library resolves them reliably. The IANA name carries the full history of this place's offset and daylight-saving rule changes, so code written against it keeps working when a government moves the clocks.
Shortcut: this page is
utctime.app/valletta, and it
also answers to
/mla
— type any of them straight into the address bar.
See every city and code →
Daylight saving
Europe/Malta is on CEST (UTC+02:00) — its daylight-saving clock.
next change: Sunday, 25 October 2026, 02:00 local → CET (72 days away, clocks go back 60 minutes)
Computed from the IANA tz database at the moment you loaded this page, not from a date we typed in — if the rules change, this line changes with them.
A timestamp from Valletta, in every format rendered in this zone · copy any row
| Format | Value | Copy |
|---|---|---|
ISO 8601 (local, with offset) What a timestamp from this zone should look like |
2026-08-13T09:43:57+02:00 | |
RFC 3339 (local) The JSON-API form, offset preserved |
2026-08-13T09:43:57+02:00 | |
ISO 8601 (UTC) The same instant, normalised to UTC |
2026-08-13T07:43:57Z | |
Unix timestamp Identical everywhere — epoch time has no timezone |
1786607037 | |
Unix milliseconds Also zone-independent |
1786607037202 | |
RFC 2822 (local) Email Date: header from this zone |
Thu, 13 Aug 2026 09:43:57 +0200 | |
Date (local) Calendar date here, which can differ from UTC |
2026-08-13 | |
Time (local, 24-hour) Wall-clock time here |
09:43:57 | |
Time (local, 12-hour) Wall-clock time with AM/PM |
09:43:57 AM | |
UTC offset Current offset, including any daylight saving |
+02:00 | |
IANA identifier The only form you should hard-code |
Europe/Malta | |
ISO week date (local) Year-week-weekday here |
2026-W33-4 |
The Unix timestamp does not change here.
Epoch time counts seconds since 1970-01-01T00:00:00Z and is the same integer
at the same instant everywhere on Earth. Only the rendering above is
local — which is exactly why storing epoch integers makes timezone bugs
disappear, and storing bare local strings creates them.
Get the current time in Valletta using the IANA name
Python
from datetime import datetime
from zoneinfo import ZoneInfo
now = datetime.now(ZoneInfo("Europe/Malta"))
print(now.isoformat()) # local time with offset
print(now.tzname()) # current abbreviation
print(int(now.timestamp())) # unix — same number everywhereJavaScript
const tz = 'Europe/Malta';
const now = new Date();
console.log(now.toLocaleString('en-GB', { timeZone: tz }));
// ISO 8601 with the zone's offset:
console.log(new Intl.DateTimeFormat('sv-SE', { timeZone: tz,
dateStyle: 'short', timeStyle: 'medium' }).format(now));Go
loc, err := time.LoadLocation("Europe/Malta")
if err != nil { log.Fatal(err) }
now := time.Now().In(loc)
fmt.Println(now.Format(time.RFC3339))Java
import java.time.*;
ZonedDateTime now = ZonedDateTime.now(ZoneId.of("Europe/Malta"));
System.out.println(now); // with offset
System.out.println(now.toInstant()); // UTC instantC#
var tz = TimeZoneInfo.FindSystemTimeZoneById("Europe/Malta");
var now = TimeZoneInfo.ConvertTime(DateTimeOffset.UtcNow, tz);
Console.WriteLine(now.ToString("o"));Rust
// chrono = "0.4", chrono-tz = "0.9"
use chrono::Utc;
use chrono_tz::Tz;
let tz: Tz = "Europe/Malta".parse().unwrap();
let now = Utc::now().with_timezone(&tz);
println!("{}", now.to_rfc3339());PHP
$now = new DateTimeImmutable('now', new DateTimeZone('Europe/Malta'));
echo $now->format(DATE_ATOM), PHP_EOL;SQL — PostgreSQL
SELECT now() AT TIME ZONE 'Europe/Malta' AS local_time,
extract(epoch FROM now())::bigint AS unix_seconds;Bash
TZ='Europe/Malta' date +"%Y-%m-%dT%H:%M:%S%z"
TZ='Europe/Malta' date # human readableConvert
Looking for sunrise, day length or a meeting overlap?
That is the consumer view, and it lives on our sibling site.
worldclock.free (their city index).
This page stays focused on offsets, identifiers and formats.
Valletta time zone questions
What is the UTC offset in Valletta right now?
Valletta is UTC+02:00 — 2 hours ahead of UTC. The abbreviation currently in force is CEST, and the local time is 09:43 on Thursday, 13 August 2026.
Which timezone identifier should I use for Valletta in code?
Europe/Malta. Pass that string to ZoneInfo in Python, ZoneId.of in Java, time.LoadLocation in Go, or the timeZone option of Intl.DateTimeFormat in JavaScript. Do not store UTC+02:00 as a fixed offset and do not store the abbreviation CEST — the offset changes with the seasons and with the law, and the identifier is what carries those rules.
When do the clocks next change in Valletta?
On Sunday, 25 October 2026 at 02:00 local time, 72 days from now, when the clocks go back 60 minutes and the zone switches to CET (UTC+01:00). That date comes from the current IANA tzdata rules, so it tracks any change in the law rather than a value we typed in.
Does the Unix timestamp change in Valletta?
No — and this is the most common misconception about timezones. A Unix timestamp counts seconds since 1970-01-01T00:00:00Z and is the same integer at the same instant everywhere on Earth. Only the rendering changes. If your database stores an epoch integer you have no timezone problem; if it stores '2026-01-01 09:00:00' with no offset, you do.
What airport and city codes point at Valletta?
This page also answers to MLA. They all redirect here, because Valletta has one canonical page rather than one per code.