Asia/Qatar time zone

5:38PMUTC+3

UTC+3UTC+3+8 h vs New York (you)

No transitions: Asia/Qatar stays on UTC+3.

About Asia/Qatar

Asia/Qatar is the IANA time zone for Qatar and Bahrain. It currently keeps UTC+3 all year.

The zone serves 2 countries or territories because their clocks have agreed since 1970; tzdata lists them together in zone1970.tab. That says nothing about borders or sovereignty, as the file’s header points out.

Its principal location is Qatar at 25.28° N, 51.53° E.

Rule for future years (POSIX TZ string)

<+03>-3

The standard time is called “+03” (a numeric abbreviation) and is UTC+3. POSIX writes the offset with the opposite sign (west of Greenwich is positive), which is why the string says "-3". There is no daylight saving rule: the zone stays on this offset for every year after the end of its explicit transitions. Software that has no full tzdata copy, such as many embedded devices, can use this string directly as the TZ environment variable.

History of Asia/Qatar since 1970

The record starts with local mean time (UTC+3:26), which ended on December 31, 1919. The record shows no daylight saving time at any point.

YearsClocksAbbreviations
1970–1971UTC+4 all year—
1972UTC+4 until June 1, then UTC+3—
1973 onwardUTC+3 all year—

Before 1970

1 offset change before 1970 in the record:

Changes of the winter (standard) offset: Thursday, June 1, 1972, UTC+4 → UTC+3.

tzdata commits to accuracy from 1970 for every zone (zone1970.tab); earlier entries are historical research and may be incomplete.

Aliases and zones with the same clock

These older or country-specific IDs are links to Asia/Qatar in tzdata. Their pages redirect here: Asia/Bahrain.

Other zones that keep exactly the same time under the current rules (but have a different history): Africa/Nairobi, Asia/Amman, Asia/Baghdad, Asia/Damascus, Asia/Riyadh, Europe/Istanbul, Europe/Kirov, Europe/Minsk, Europe/Moscow, Europe/Simferopol, Europe/Volgograd.

Places on Asia/Qatar

Convert Qatar time

Tip: Alt+↑/↓ steps the time by 15 minutes (Shift: one hour). The link keeps the date, time and direction.

Using Asia/Qatar in code

Every major platform reads the same IANA ID. Store instants in UTC and convert with the ID at display time; never store a fixed offset for a place that has daylight saving time.

// JavaScript
new Date().toLocaleString('en-US', { timeZone: 'Asia/Qatar' })

# Python 3.9+
from zoneinfo import ZoneInfo
from datetime import datetime
datetime.now(ZoneInfo('Asia/Qatar'))

// Java
java.time.ZonedDateTime.now(java.time.ZoneId.of("Asia/Qatar"))

// Go
loc, _ := time.LoadLocation("Asia/Qatar")
time.Now().In(loc)

-- PostgreSQL
SELECT now() AT TIME ZONE 'Asia/Qatar';

# Shell
TZ='Asia/Qatar' date

Platforms ship their own copy of tzdata and update it on their own schedule. After a rule change, outputs can differ until the platform updates; this page uses tzdata 2026f.

Questions

What is the UTC offset of Asia/Qatar?
UTC+3 all year.
Does Asia/Qatar observe daylight saving time?
No, not under the current rules.
Is Asia/Bahrain the same as Asia/Qatar?
Yes. Asia/Bahrain is a link (alias) to Asia/Qatar in tzdata and gives the same time since 1970. It remains a valid ID.
Which countries use Asia/Qatar?
Qatar and Bahrain, according to zone1970.tab in tzdata.

Related