Three kinds of time value
The number 90 min is an elapsed duration and equals 1.5 hours. The display 01:30 is a clock reading if it means half past one, but it can also be a duration notation meaning one hour and thirty minutes. An ISO 8601-style string with a date, time and UTC offset identifies an instant. Unix time counts seconds from its epoch for that instant. Before choosing a converter, ask which kind of value the source system stored. A plain hour-and-minute converter has no date or offset and cannot place an event on a global timeline.
A worked timestamp example
Take 2026-10-24T10:00:00+02:00. The explicit +02:00 offset means the same instant as 2026-10-24T08:00:00Z. Enter the first string in the embedded ISO-to-Unix converter and compare its output with the second string in the same tool. They should produce the same epoch-second value, because the display clocks differ while the instant is identical. The conversion does not establish that +02:00 is the legal civil offset for every region on every date; it simply applies the offset written in the input. A region name requires separate time-zone rules.
- 90 min → 1.5 h duration
- 10:00 +02:00 → 08:00 Z, same instant
- Named region → consult time-zone rules
Why local clocks can mislead
A booking says 10:00 in one city and a colleague reads 10:00 in another. These are not necessarily the same instant. During a daylight-saving change, some local clock times repeat and others do not occur at all. A fixed numeric offset in an ISO timestamp removes the ambiguity for that particular event, but it does not tell a scheduler what offset the same named location will use next month. Store an instant together with a named time zone if future local scheduling matters. Use the IANA database or the destination calendar system to resolve region rules.
Add a duration to an instant carefully
For a simple fixed elapsed interval, 90 min is 5,400 seconds. Adding that count to an epoch timestamp gives a later instant, even if the displayed local clock changes across a daylight-saving boundary. Adding one calendar day is a different instruction: the local clock target may be 23, 24 or 25 elapsed hours away around a transition. The minute-to-hour tool only changes how a duration is expressed; the ISO-to-Unix tool interprets an instant. Keep these operations separate in a log, timesheet or travel itinerary.
A safe exchange format
For event logs, include the full date, seconds if needed and an offset or Z in each timestamp. For appointments tied to a place, retain its time-zone identifier as well. For working time, record elapsed minutes or hours with the start and end instants if they must be audited. Avoid assuming that a trailing Z is interchangeable with a local clock value: Z means UTC. When comparing two events, convert both instants to a common basis first, then subtract to obtain duration. That order prevents an apparently simple hours conversion from hiding a calendar rule.