DUR2HOURS Function in Apple Numbers: Syntax, Examples and Troubleshooting

• Introduced: Documented in Apple’s Formulas and Functions Help 15.4; the original introduction release is not established.
• Availability: Supported by the current Apple Formulas and Functions Help 15.4 documentation for Numbers; no final supported-version endpoint is identified.
• Scope: Shared iWork function reference; the formatting steps below refer to Numbers for Mac. Older releases and individual-client introduction dates are not established here.
• Checked: October 14, 2026, against the official DUR2HOURS reference. Documentation and independent arithmetic checks; no native Numbers test.

=DUR2HOURS(duration)

duration is the single required argument: an elapsed-time value, or a reference to a cell containing one. There is no optional conversion mode or documented default input. The output is a number of hours, rather than another duration value. Apple describes the input type in its argument and value guide.

For predictable practice data, create the duration with DURATION instead of relying on how a colon-separated text entry is interpreted. A bare number such as 1.5 does not state whether you mean days, hours or minutes; put it in the correct DURATION argument first. The formulas here use English-language commas and decimal points; use the function editor’s local syntax if your document uses different separators.

Create a Numbers table with at least six columns and eleven rows. Use A1 for Description, B1 for Duration and C1 for Total hours. Enter the following formulas in B2:B7; do not type them as quoted text.

In C2, enter =DUR2HOURS(B2) and fill down through C7. C3 should refer to B3, and so on. Set C2:C7 to Number, with enough decimal places to inspect small results. Values marked ≈ are rounded here for display, not instructions to round the stored result.

A duration can exceed a day and can be negative. The negative row represents a signed time adjustment; the zero row is an explicit zero duration, not an empty cell. Do not replace the required argument with a blank and assume the same behavior.

One hour corresponds to 3,600,000 milliseconds, or 60 minutes. Divide the total elapsed milliseconds by 3,600,000 to check the result. This dimensional calculation is independent of a cell’s chosen display style.

Keep the practice table. Put =DURATION(0,0,2,30) in B10 and =DURATION(0,0,1,45) in B11. These are two hours thirty minutes and one hour forty-five minutes. In C10, enter =DUR2HOURS(B10), then fill down to C11. The expected outputs are 2.5 and 1.75 hours.

Type the numeric hourly rate 80 in E10. Put =(C10+C11)*E10 in F10. The expected amount is 340: 4.25 hours multiplied by 80 currency units per hour. You can format F10 as Currency without changing that arithmetic. Do not enter 2.30 to mean two hours thirty minutes; decimal 2.30 hours is only two hours eighteen minutes.

If a contract rounds each entry to a billing increment, apply that rule explicitly before multiplication. Merely reducing the displayed decimal places in C10:C11 does not change their stored values. See ROUND for deliberate numeric rounding rather than display formatting.

• The result seems to lose precision: show more decimal places. On Mac, select the result cell, open Format > Cell, choose Number, and adjust Decimals. Apple’s formatting guide explains that displayed rounding does not change the value used in subsequent calculations.
• The input is a clock time: a date/time value and an elapsed duration are different types. Use TIME for a time of day, or construct the elapsed quantity with DURATION. Do not infer duration units from how a clock-style string looks.
• The formula is rejected: check the function spelling, the one required input, and whether B2 contains a real duration-producing formula. The function page does not enumerate exact error labels for every invalid text, missing argument or out-of-range case, so no particular error code is promised here.
• A downstream calculation fails: inspect its denominators and unit labels before wrapping it in IFERROR. Hiding an error does not fix an input expressed in the wrong unit.

The examples use exact millisecond arithmetic. Undocumented input coercion and precision limits remain unverified; displayed decimal places alone do not establish those limits.