Skip to content

Main content

Date: Utc Offset Minute Component Check Tool

Parse a restricted signed HH:MM UTC offset with minute validation and explicit -00:00 unknown-local-offset evidence; no timezone database.

Loading tool…

Description

Parse a restricted signed UTC offset token.

A fixed UTC offset differs from a named timezone whose rules can vary by date. A zone-like label or signed-zero offset also carries metadata that a numeric minute total alone cannot express.

Parse a restricted signed UTC offset token.

When to use this tool

Use Date: Utc Offset Minute Component Check when inspecting a supplied offset or timezone annotation.

How to use the tool and how it works

  1. Enter offsetToken. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Parse a restricted signed UTC offset token. Require ±HH:MM with hours 00-23 and minutes 00-59; offsetMinutes applies the sign, and negativeZeroUnknown identifies exact -00:00.1

RFC 3339 distinguishes an unknown local offset from known UTC and restricts leap-second notation to appropriate actual time contexts; lexical parsing does not verify those contexts.2

Input fieldMeaning and unitsAccepted input
offsetTokenOffset TokenRequired. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
Output fieldInterpretationReturned shape
resultReturned object; expand its named members below.Required. Object.
result.offsetMinutesOffset MinutesCalculated result member: number.
result.negativeZeroUnknownTrue for the negative-zero offset spelling; numeric offsetMinutes is still zero.Calculated result member: boolean.
json
{
  "input": {
    "offsetToken": "-05:30"
  },
  "output": {
    "result": {
      "offsetMinutes": -330,
      "negativeZeroUnknown": false
    }
  }
}

Limitations and assumptions

  • This is a numeric offset, not an IANA zone lookup; signed-zero metadata must be read separately.
  • Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use an authoritative timezone database and complete timestamp context to resolve an actual local time or day.

References

  1. Calculation and input contract: date/utc-offset-minute-component-check — tool.io

  2. RFC 3339: Internet timestamps — RFC Editor

Similar or alternative tools