Contact

TIMEVALUE in WPS Spreadsheet: Parse Time Text Without Losing Duration Context

Date & Time Intermediate WPS Spreadsheet

Parse WPS time text into day fractions, compare 12-hour and 24-hour inputs, and handle same-day or explicit overnight duration calculations.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: TIMEVALUE(time_text) converts a recognized time string into a fractional-day value. The WPS lesson documents both 12-hour and 24-hour text and says recognized date information is ignored. Preserve dates separately when a duration crosses midnight or lasts more than a day.

Availability and version history

  • Introduced: documented by 2019-06-11 in the official WPS lesson; original introduction is not established.
  • Availability: WPS Office for Windows Personal; the lesson metadata gives no numeric release.
  • Scope: exact current supported builds remain unverified; the historical Windows lesson does not establish all WPS clients.
  • Checked: October 14, 2026 against complete function-specific documentation. Examples are independent expectations; no native WPS test was performed.

Syntax and parsing scope

=TIMEVALUE(time_text)

Use quoted text or a cell containing recognized time text. The exact accepted strings depend on the relevant input conventions, so verify the provided English AM/PM controls in the intended workbook locale. A fraction of 0.5 represents noon.

The source walkthrough suggests storing imported text as text first. That is useful for a controlled parsing exercise; it does not mean genuine numeric time values cannot be subtracted directly. This guide distinguishes text conversion from ordinary arithmetic on already valid values.

Example 1: compare equivalent text inputs

=TIMEVALUE("6:45 PM")
=TIMEVALUE("18:45")
=TIMEVALUE("12:00 PM")

Documented-model expectations are 0.78125, 0.78125 and 0.5. With a time display, the first two show 18:45:00 and the last 12:00:00. The equivalent first two strings are specifically represented by the WPS source’s input examples.

Formatting the source text as a time does not establish that conversion occurred. Keep the original text beside the parsed value while checking an import.

Example 2: calculate a same-day interval

In A2 enter ="17:00"; in B2 enter ="19:30". These formulas create explicit text. Then calculate:

=TIMEVALUE(B2)-TIMEVALUE(A2)
=(TIMEVALUE(B2)-TIMEVALUE(A2))*24
=(TIMEVALUE(B2)-TIMEVALUE(A2))*1440

Expected results are 5/48 of a day, 2.5 hours and 150 minutes. The second and third outputs should be ordinary numbers with clearly labeled units. They are not hour or minute components.

Advanced example: preserve the overnight assumption

Suppose start text is 23:30 and end text is 01:15. Direct time-only subtraction yields −22.25 hours. If the business record explicitly says the end is on the next day, use that known one-day offset:

=(1+TIMEVALUE("01:15")-TIMEVALUE("23:30"))*24

Expected duration: 1.75 hours, or 105 minutes. The +1 means one whole day; it is an explicit assumption supplied by the record, not something TIMEVALUE infers.

If an interval could span several days, a negative-time wrap shortcut can hide an input error or erase complete days. Store both actual dates and times instead.

Advanced example: combine separately recorded dates and text times

Create start date A5 with =DATE(2026,10,14) and end date B5 with =DATE(2026,10,16). Let C5 contain ="23:30" and D5 ="01:15":

=((B5+TIMEVALUE(D5))-(A5+TIMEVALUE(C5)))*24

Expected duration: 25.75 hours. A time-only next-day assumption would instead give 1.75 and lose a full day. Keep the complete timestamp construction visible when reviewing logs.

Ignored dates and unresolved inputs

The formal definition says date information in recognized time text is ignored. It follows that TIMEVALUE alone cannot preserve a complete timestamp. This guide avoids certifying a universal combined date-time string format because locale and parsing details are not pinned.

Subsecond parsing, numeric arguments, missing fields, invalid-input error codes, Boolean/blank coercion and every AM/PM spelling remain unverified. Use TIME when the source already provides numeric components. Use DATEVALUE only for its separate date-text task.

The broad walkthrough claim that times cannot be calculated directly is misleading. Numeric day fractions can be used in ordinary arithmetic; TIMEVALUE is needed when the starting information is recognized text requiring conversion.

References and verification

The complete function definition and walkthrough were reviewed. Worked outputs are independent calendar and time models; source ambiguities and native boundaries remain explicit.