Local time from UTC offset calculator

Enter the UTC time, a city label, and the signed hour and minute components of the offset. The result shows the local time and whether it falls on the previous, same, or next calendar day. No timezone lookup, network request, system clock, or daylight-saving assumption affects the calculation, so the same input always produces the same output.

Enter the UTC reference time and city

Start with a reference time expressed in Coordinated Universal Time and write it in strict 24-hour HH:MM format. Midnight is 00:00, noon is 12:00, and the final valid minute is 23:59. The city field is a label for the result, not a request to look up geographic data. For example, entering Kathmandu does not cause the calculator to contact a timezone service or decide which offset currently applies there. You must supply the appropriate offset for the date and circumstances yourself. This distinction matters because cities can observe daylight-saving changes, governments can alter civil-time rules, and historic offsets may differ from present ones. The calculator deliberately handles the arithmetic after that policy decision has already been made. Use a trustworthy schedule or official source to find the applicable offset, then enter it with the UTC reference time. Strict input formatting prevents ambiguous values such as 7:5, while the retained city label makes the returned object easy to display in itineraries, dashboards, reports, and messages without pretending that the calculator verified the location.

Provide the signed UTC offset components

Enter the whole-hour component in offset_hours and the remaining minute component in offset_minutes. Positive components describe a clock ahead of UTC, while negative components describe one behind UTC. A +05:45 offset is represented by 5 hours and 45 minutes; a -03:30 offset is represented by -3 hours and -30 minutes. The two nonzero components must use the same sign so that the intended direction is explicit. For an offset smaller than one hour behind UTC, use zero hours and a negative minute value. The complete supported range runs from -12:00 through +14:00, which covers the range of standard civil offsets while keeping obviously mistaken values out. Minute components must be whole numbers between -59 and 59, so fractional or oversized minute fields are rejected rather than rounded or silently carried. Once validated, the calculator converts the entire offset to signed minutes and adds it to the UTC minutes after midnight. This direct representation also supports common half-hour and quarter-hour offsets without floating-point arithmetic or a lossy decimal-hours conversion.

Read the local time and calendar-day shift

The local_time field is the converted clock value in zero-padded 24-hour HH:MM format. The day_offset field explains how the local calendar day relates to the calendar day containing the supplied UTC time: -1 means the previous day, 0 means the same day, and 1 means the next day. For example, adding a large positive offset late in the UTC day can cross midnight and produce 1, while applying a negative offset shortly after UTC midnight can produce -1. This calculator receives no calendar date, so it does not invent a month, weekday, or date after a boundary crossing; callers can apply day_offset to their own known date using an appropriate calendar system. The returned offset components are included alongside the city and both clock values, making the calculation auditable without parsing prose. Because the implementation uses bounded integer arithmetic only, it has no dependency on the machine's locale, timezone, current time, or daylight-saving configuration. Invalid times, empty city labels, inconsistent offset signs, and out-of-range totals produce a typed invalid-input error. API use costs $0.002 per request, and the same pure solver can execute in the browser.