TIME in Excel: Build Clock Times and Handle Overflow
Build Excel times from numeric components, check carried minutes and seconds, and distinguish wrapped clock time from elapsed duration.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: TIME combines hours, minutes and seconds into a fraction of a day. It represents a clock time, so hours beyond 23 wrap around the 24-hour clock rather than preserve a multi-day duration.
Availability and version history
- Introduced: first introduction version is not established by the official history reviewed; the current product list is not a launch record.
- Availability: official help lists Excel for Microsoft 365, Excel for Microsoft 365 for Mac, Excel 2024, Excel 2024 for Mac, Excel 2021, Excel 2021 for Mac, Excel 2019, Excel 2016.
- Checked: October 14, 2026; official TIME reference. Documentation and independently modeled examples; no native Excel execution or broader platform certification.
Syntax and documented component ranges
=TIME(hour, minute, second)
All three arguments are required. Microsoft documents numeric component values from 0 to 32767. Hours above 23 are reduced modulo 24; excess minutes and seconds are carried into larger time units. The examples use nonnegative integer components within those documented ranges.
Format the result as time to see a clock display, or as Number to inspect its day fraction. The function constructs a value; it does not choose a time zone, look up the current time or record an event automatically.
Example 1: reconstruct a working-day start time
=TIME(8,30,0)
=TIME(12,0,0)
=TIME(0,0,0)
Expected day fractions are approximately 0.354166667, 0.5 and 0. Their clock displays are 08:30, 12:00 and 00:00. The first is 8.5/24; noon is half a day.
A numeric zero is a valid midnight time here. It should not automatically be interpreted as a missing value just because a report sometimes uses blanks for unentered times.
Example 2: combine separate input columns
Enter this A1:C4 table, with numeric components:
| Hour | Minute | Second |
|---|---|---|
| 8 | 15 | 30 |
| 13 | 45 | 0 |
| 23 | 59 | 59 |
In D2 enter =TIME(A2,B2,C2) and fill down. Expected times are 08:15:30, 13:45:00 and 23:59:59. Their exact day fractions are 29730/86400, 49500/86400 and 86399/86400.
These inputs remain separate from the output cells, so filling down does not accidentally include a calculated time as a later hour argument.
Advanced example: carry oversized minutes and seconds
=TIME(0,90,0)
=TIME(0,0,125)
=TIME(1,75,90)
Expected times are 01:30:00, 00:02:05 and 02:16:30. The final control totals 3600+75*60+90, or 8190 seconds; dividing by 86400 gives approximately 0.094791667.
The source illustrates this normalization rule but has a typo in its 2000-second example: 2000 seconds is 33 minutes 20 seconds, not 33 minutes 22 seconds. The new controls above are independently calculated from integer totals.
Normalization can be useful, but it is not validation. If minutes in an imported clock field must lie between 0 and 59, reject 90 under that input policy rather than accepting its normalized output as proof that the original field was valid.
Advanced example: clock wrapping loses complete days
=TIME(27,0,0)
=TIME(24,0,0)
Expected times are 03:00 and 00:00, represented by 0.125 and 0. The complete day in 27 hours does not survive in the TIME result.
For a duration of 27 hours, the numeric day quantity is instead 27/24, or 1.125. Multiplying it by 24 recovers 27 hours. Multiplying the TIME result 0.125 by 24 gives only 3, so the two values cannot be substituted for one another.
Likewise, 1500 minutes represents 25 elapsed hours, but TIME(0,1500,0) supplies the clock time 01:00. Choose whether the input means a time of day or an accumulated duration before choosing the formula.
Advanced example: attach a time to an explicit date
=DATE(2026,10,14)+TIME(8,30,0)
The expected displayed timestamp is October 14, 2026 at 08:30. In the 1900 date system its serial is approximately 46309.354166667. The date component comes from DATE, not from TIME.
Adding TIME(27,0,0) to that date produces October 14 at 03:00, not October 15 at 03:00. To advance 27 hours from midnight, add 27/24 instead. This contrast makes the lost-day boundary explicit.
Verify components and retain remaining holds
For the 08:15:30 control, HOUR, MINUTE and SECOND have expected outputs 8, 15 and 30. They provide component checks, not an independent native execution of TIME.
The captured TIME reference does not establish a complete error-code or coercion table for negative values, values beyond 32767, numeric text, blanks or fractional component arguments. Those cases remain separate native tests rather than inferred from another spreadsheet.
References and verification
Expected results are independent calendar/arithmetic models or explicitly documented rules, not captured native output. Examples use English function names and comma separators. Input dates and schedules are fictional.