Asia/Riyadh

TZ identifier and aliases

Asia/Riyadh is the canonical identifier for Saudi Arabian time, covering the entire country. Asia/Aden (Yemen) and Asia/Kuwait currently share identical rules and are folded into the same entry — three separate countries whose civil time happens to align rather than one being an alias of another. Asia/Riyadh has no deprecated backward-compatibility alias of its own.

UTC offset and DST rule

Asia/Riyadh is +03:00 year-round with no daylight saving time. Saudi Arabia has never observed DST, so there's no seasonal clock change to account for in any system built against this zone.

Using it in cron, CI and Postgres

Set TZ=Asia/Riyadh for a process that should schedule by Saudi local time. Postgres accepts it via SET TIME ZONE 'Asia/Riyadh'; or the timezone setting. Because the offset never changes, a cron job's local-time schedule behaves identically every day of the year, with no DST boundary or skipped/duplicated hour to plan around — useful for any system coordinating with Gulf-region business hours, which additionally often run Sunday–Thursday rather than the Monday–Friday week assumed by most default scheduling tooling, a separate but related gotcha worth checking for regional deployments.

History and quirks

Saudi Arabia historically used an unusual sunset-based timekeeping convention in parallel with standard civil time — a system where the new day began at sunset, similar to some traditional lunar-calendar practices — before fully standardizing on +03:00 as the sole civil time reference in the mid-20th century, a shift tied to the growth of modern infrastructure, aviation and international trade that required predictable clock alignment with the rest of the world. Like its Gulf neighbors, Saudi Arabia's low latitude means day length barely changes across the seasons, removing the practical rationale that DST proponents cite in higher-latitude countries. Asia/Riyadh's offset, +03:00, matches Moscow's winter time and sits exactly between the EU's Central European zones and India's +05:30, making it a common middle point for scheduling calls that span Europe and South Asia.

Saudi Arabia's civil calendar adds a second layer of complexity beyond the time zone itself: government and religious scheduling often runs on the Hijri (Islamic lunar) calendar alongside the Gregorian one used for international business, and while that calendar choice has no effect on Asia/Riyadh's UTC offset, it does affect which Gregorian dates count as public holidays or weekend days in a given year, since Hijri dates shift roughly eleven days earlier relative to the Gregorian calendar annually. Any system localizing for Saudi users needs to handle that calendar distinction separately from the timezone question Asia/Riyadh itself answers — the offset is simple and fixed, but the calendar layered on top of it is not.

Offsets and DST transitions on this page are computed from the IANA time zone database bundled with your browser; the rules described above were verified against tzdata 2026b when this page was published.