Contact

TIMEVALUE Function (OpenOffice Calc)

Date & Time Intermediate OpenOffice Calc

Convert time text to a fraction of a day with Apache OpenOffice TIMEVALUE. Verify seconds, midnight, date-time extraction and locale-sensitive parsing.

Verification status: Eight ordinary 24-hour time-text formulas were recalculated in Apache OpenOffice 4.1.16 on Linux x86-64, Build 9816, using generated ODF. Saved identities, typed results and controls were checked. Locale was English (USA), default currency USD; other locales were not tested. How formula examples are checked

Quick answer: =TIMEVALUE("00:00:00") returned 0 as a numeric value in the tested date system and locale.

Availability and version history

  • Introduced: First release not established; documented by OpenOffice.org 3.3.
  • Supported in: Apache OpenOffice 4.1.16; no final supported release is established.
  • Scope: English desktop Calc with semicolon-separated formulas. The observed locale was English (USA), default currency USD.
  • Checked: October 14, 2026. Eight ordinary examples were recalculated in 4.1.16 on Linux x86-64, Build 9816. Saved types, strings or numeric values, and both controls were checked.

What TIMEVALUE returns

TIMEVALUE returns the fractional day represented by text recognized as a time or date-time. The implementation subtracts the floor of the parsed serial, retaining its time fraction rather than a count of elapsed seconds. Release implementation.

Syntax and arguments

=TIMEVALUE(Text)
  • Text: a string recognized by the active number-format parser as a time or date-time.

The examples use ordinary 24-hour hour:minute:second strings. The tested scope does not include every locale’s AM/PM notation or elapsed-duration format.

Reproducible examples

All eight formulas were recalculated. Independent references use calendar-day counts or exact seconds divided by 86400. Noninteger results are displayed to twelve decimal places; this is presentation precision, not a universal accuracy guarantee.

Formula Independent reference Saved 4.1.16 numeric result
=TIMEVALUE("00:00:00") 0 0
=TIMEVALUE("06:00:00") 0.25 0.25
=TIMEVALUE("12:00:00") 0.5 0.5
=TIMEVALUE("18:00:00") 0.75 0.75
=TIMEVALUE("01:30:00") 0.0625 0.0625
=TIMEVALUE("23:59:59") 0.999988425926 0.999988425926
=TIMEVALUE("00:00:01") 0.000011574074 0.000011574074
=TIMEVALUE("09:15:30") 0.385763888889 0.385763888889

Practical worksheet

06:00:00 is one quarter of a day, 12:00:00 is one half and 18:00:00 is three quarters. 01:30:00 is 5400/86400=0.0625. Multiplying the returned fraction by 24 gives hours; multiplying by 86400 gives seconds for these ordinary time-of-day examples.

23:59:59 is 86399/86400, approximately 0.999988425926. Midnight is zero. These are times within a day, not independently dated timestamps, and the function does not choose a time zone.

Advanced interpretation and checks

The 09:15:30 example contains 9×3600+15×60+30=33330 seconds, giving 33330/86400=0.385763888889 approximately. One second is 1/86400, a repeating decimal fraction whose saved floating-point approximation must not be confused with a terminating exact decimal.

For a recognized date-time, the source removes its integer date component. That rule does not preserve a multi-day elapsed duration as an unrestricted hour count. If the task is to measure elapsed time between two dated events, retain both complete date-time serials and subtract them instead.

Boundaries and troubleshooting

The parser must classify the text as a time or date-time. Merely supplying a numeric-looking string does not establish that classification. Invalid strings, out-of-day inputs, AM/PM variants and other locales were not executed in this set.

A time number may display as a decimal until the cell is formatted as a time. Formatting changes presentation, not the stored fraction. Conversely, a displayed clock-looking string may still be text. Keep parsing, numerical storage and display formatting as separate checks when importing schedules.

Official evidence and checking scope

The generated ODF was opened in the native application, hard-recalculated and saved separately. Its informational “Not all attributes could be read” load warning was retained. Both stale and uncached SUM controls refreshed correctly. The original XLSX was not executed, and this generated-ODF test does not establish manual entry or execution in another release or locale.