Reading clock times straight from UTC offsets
Give the date and clock time on one side along with that side's UTC offset, then list the offsets you want to compare, one per line. The table shows what the same instant reads as under every offset you listed. Because a bare clock time hides a rolled-over day, each row also carries the local date and a same day, next day or previous day tag, plus the gap from your reference. Entries such as -05:00, -0500 and -5 are all read the same way.
The math subtracts the reference offset to land on the UTC instant, then adds each listed offset. Dates are built from UTC components only, so the answer never shifts with the viewer's own device setting. Offsets from -14:00 to +14:00 are accepted, including quarter-hour, half-hour and three-quarter-hour values. (As of October 2026)
No list of cities or countries is offered. Daylight saving moves an offset within the year and the rules themselves change, so a fixed list of place names would hand out wrong values. Finding the overlapping window for a meeting is not covered either. Enter the offset printed on the schedule or invitation you are working from.
Frequently asked questions
Daylight saving changes a city's offset during the year, and the rules themselves are revised. A fixed list of place names would hand out wrong values, so the offset is taken from you.
Yes. Write the minutes, as in +05:45, and they are applied exactly. Anything from -14:00 to +14:00 is accepted.
The date column tags every row as same day, next day or previous day. Gaps of two days or more are written out as days later or days earlier.