TIME Function in Apple Numbers: Exact Syntax, Examples and Troubleshooting

Construct a time-of-day date/time value from three numeric inputs, in the official order hours, minutes, seconds. =TIME(16,45,30) is expected to represent 16:45:30 (4:45:30 PM). Choose a Date & Time cell format to show the seconds.

Create clock times from numeric hour, minute and second components with overflow and decimal rules. For a reproducible time source, use Numbers’ TIME constructor rather than ambiguous local-language time strings. Preserve original imported values when cleaning data so a formula result doesn’t hide a source problem. The examples below intentionally share a dataset with the companion HOUR, MINUTE, SECOND and TIME tutorials while verifying each function’s separate contract.

=TIME(hours, minutes, seconds)

Defaults: none documented. Apple says any decimal fraction of each argument is ignored, and clock-time totals beyond 24 hours are reduced until below 24 hours. Neither rule turns TIME into a duration function.

Official behaviour: Apple explicitly documents over-24-hour normalization and discarding fractional parts, including examples for 900 minutes and 60 hours. See the official Apple TIME reference (documentation path 15.4, consulted 2026-10-11). The function-specific help does not establish a first-supported app release; do not extrapolate minimum Mac/iOS/iPadOS/web versions.

Create a Numbers table named Times. Set row 1 as its header. Enter A2:C6 as numbers, not timestrings; set D2:D6 to a Date & Time format that shows clock hours, minutes and seconds, after adding formulas. Columns E–G are formula result columns. No source CSV, external download or screenshot is required.

*The D entries describe the expected clock time. Numbers can show an AM/PM display or include a date depending on the Date & Time cell format. The rows use actual numeric inputs; do not paste the displayed D text to substitute for a time value.

In D2 enter =TIME(A2,B2,C2) and fill down to D6. Set D to a Date & Time display format that shows seconds; then you can derive E–G with HOUR, MINUTE and SECOND.

1. Create a Numbers table called Times. Make row 1 a header and enter the numeric inputs in A2:C6 shown below.
2. In D2 type =TIME(A2,B2,C2) and fill down to D6. Set the D-column display to a time format including seconds; this is presentation, not a different formula.
3. Expected D2:D6 clock components: 09:07:05, 16:45:30, 00:00:00, 23:59:59, 15:00:00.
4. The last row is intentionally unusual. Apple’s reference says =TIME(0,900,0) returns 3:00 PM: 900 input minutes normalize to 15 hours.
5. Test the day-boundary rule without relying on dates: =TIME(25,0,0) has an independently calculated expected clock time of 01:00:00 because Apple says whole-day overflows are subtracted.
6. Test the decimal rule using Apple’s official example =TIME(4.25,0,0): expected 04:00:00, since the fractional .25 hour is ignored, not converted to 15 minutes.

Normalize a scheduling export

Suppose a CSV export stores start times as three numerical fields but sometimes has 70 minutes. =TIME(A2,B2,C2) creates a clock time without requiring the editor to interpret a region-dependent string such as "4/6/88 11:59:22pm". Apple’s normalization rule means:

=TIME(10,70,15)

has the independently calculated expected clock time 11:10:15. This might be useful when upstream systems send total minutes or carry an overflow, but it could also conceal a data-quality defect. Keep the raw hour/minute/second fields in the original columns for auditing.

Distinguish clock time from work duration

=TIME(60,0,0) is documented by Apple to return 12:00 PM after modulo-24 normalization. It does not preserve 60 hours of elapsed labour time. For timesheets or SLA measurements spanning multiple days, use actual date/time stamps and Numbers duration functions designed for intervals rather than treating TIME as an elapsed-hours datatype.

A useful checking column is =HOUR(D2), which should agree with the normalized hour component of the TIME result rather than blindly echo the unvalidated source input.

• Argument order: =TIME(hours,minutes,seconds) is the only documented signature. It has three required numeric arguments. TIME(16,45) omits one; TIME("4:45 PM") is not the documented constructor.
• Unexpected midnight or 3 PM: oversized inputs normalize modulo 24 hours, so TIME(0,900,0) becomes 15:00, not 900 minutes of duration.
• Fractions ignored: Apple’s documentation says fractional portions of each numeric argument are ignored. TIME(4.25,0,0) gives 04:00, not 04:15.
• Appearance without seconds: a cell may show 4:45 PM even if the underlying value has seconds. Choose a time format displaying seconds before concluding they were lost.
• Negative or invalid/non-numeric input: the retrieved Apple TIME page does not establish every negative-value or text-coercion edge case. Do not assert a normalization result without testing; inspect source cell types.
• Date component confusion: the result is a date/time value; don’t infer from a displayed clock time alone which calendar date or timezone an application associated with it.
• Cross-table inputs: in another table use qualified references, e.g. =TIME(Times::A2,Times::B2,Times::C2), rather than Excel-style Times!A2 notation.

This tutorial was checked against Apple’s English Formulas and Functions Help 15.4 on 2026-10-11. The 15.4 in a documentation URL describes the help edition. It does not establish a function’s first-supported Numbers release or prove identical execution across macOS, iOS, iPadOS and iCloud.com. Apple documents a Functions Browser in Numbers on Mac, iPhone, iPad and on iCloud.com, but none of those native app editions was used to run these examples. Treat historical releases as unverified unless their own documentation is checked.

Use normal Numbers table references, not Excel worksheet notation: A2 is a same-table cell; Times::D2 is the unambiguous cross-table form when a table named Times is elsewhere on the sheet; Sheet 2::Times::D2 names a sheet and table when required. Apple’s cell-reference help documents the double-colon form. When editing, select the desired cell to have Numbers construct the reference rather than typing a guessed table prefix.

The English examples separate function arguments with commas. Apple’s functions overview instructs users whose regional settings use a comma decimal separator to use semicolons between function arguments when typing by hand. For example, change =TIME(9,7,5) to =TIME(9;7;5), but do not change punctuation inside quoted text. Displayed date/time order and AM/PM appearance are formatting/localization issues, not a different formula signature. Avoid relying on interpretation of ambiguous imported time strings.

The names of these common date/time component functions occur in other spreadsheet products, but matching names do not certify identical handling of imported text, time zones, date serials, errors, or special inputs. The examples here are grounded in Apple’s documented Numbers syntax. Copying Excel Sheet1!D2 references or a Google Sheets tab-qualified formula into Numbers is not a direct substitute for Numbers table references (Times::D2). A number representing clock time is not the same as a duration; elapsed working time across midnight needs a separately designed calculation, not merely a component extractor. Cross-application execution and conversion were not tested.

• COUNTIFS: count records meeting multiple conditions
• SUMIFS: total records meeting multiple conditions

For related time functions, these direct Apple documentation links provide the primary syntax references: TIME, HOUR, MINUTE, SECOND.

• Apple Numbers — function documentation
• cell-reference help
• functions overview
• HOUR
• MINUTE
• SECOND
• Apple: Formulas and Functions Help

Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in Apple Numbers.

• No genuine Apple Numbers screenshots are included; this guide does not use mock application images.