Pattern

Regex for Timezone offset

UTC offset in ±HH:MM or ±HHMM format.

The Timezone offset regex is ^[+-](0\d|1[0-4]):?[0-5]\d$ — copy it below, or open it in the explainer for a token-by-token breakdown.

The pattern

^[+-](0\d|1[0-4]):?[0-5]\d$

Try in explainer → Download cheat sheet ↓

What it matches

+05:30
-08:00
+0530
-0800
+00:00

What it doesn't match

+15:00
-13:99
+5:30
UTC+5

Notes & gotchas

Hours 00–14 (real timezones range from -12 to +14), minutes 00–59. Colon optional. Z is not matched — use a separate regex for that.

Code in your language

Use the explainer's Code tab to generate ready-to-paste snippets in JavaScript, Python, Java, .NET, Go, Ruby, and PHP for this pattern.

Open in explainer →

Token-by-token breakdown

Every part of the pattern, left to right:

Token	Meaning
`^`	start of string (or line in multiline mode)
`[+-]`	any of: “+”, “-”
`(`	start of a capturing group
`0`	literal text “0”
`\d`	any digit (0–9)
`\|`	OR — try the alternative
`1`	literal text “1”
`[0-4]`	any of: 0–4
`)`	end of group
`:?`	optional (zero or one): the literal “:”
`[0-5]`	any of: 0–5
`\d`	any digit (0–9)
`$`	end of string (or line in multiline mode)

About this pattern

Date and time formats vary enormously across regions and systems. The regex here validates structure only — a date like 2024-02-30 would pass format validation but isn't a real date. After regex passes, parse with your language's date library to confirm semantic validity.

Quick usage in different languages

This exact pattern — with the correct escaping and idioms for each language:

JavaScript: /^[+-](0\d|1[0-4]):?[0-5]\d$/.test(value)
Python: re.match(r"^[+-](0\d|1[0-4]):?[0-5]\d$", value)
Java: Pattern.compile("^[+-](0\\d|1[0-4]):?[0-5]\\d$").matcher(value).matches()
C# / .NET: Regex.IsMatch(value, @"^[+-](0\d|1[0-4]):?[0-5]\d$")
Go: regexp.MustCompile(`^[+-](0\d|1[0-4]):?[0-5]\d$`).MatchString(value)
Ruby: /^[+-](0\d|1[0-4]):?[0-5]\d$/.match?(value)
PHP: preg_match('~^[+-](0\d|1[0-4]):?[0-5]\d$~', $value)

The explainer’s Code tab regenerates these for any pattern you paste, and the downloadable cheat sheet bundles the breakdown, all seven snippets, and the pitfalls below onto one printable page.

Common pitfalls

Anchored to the whole string. This pattern uses ^ and $, so it requires the entire input to match. To find it inside a longer text, drop the anchors and use the global (g) flag.
Escape it correctly per language. In Java and JavaScript strings each backslash must be doubled (\\d); in Python, Go, and C# use raw/verbatim strings so the backslashes survive.
Validate beyond format. Matching the format doesn't guarantee the value is real. Confirm the timezone offset against a source of truth (database, API, or checksum) where it matters.

Standards & sources

This pattern is based on the following authoritative specification(s) and issuing authorities. Formats can change — always confirm against the primary source.

ISO 8601 — Date and time format

Related patterns

More patterns in the Date & time category: