TIMEVALUE in Excel: Convert Time Text Without Keeping the Date

• 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 TIMEVALUE reference. Documentation and independently modeled examples; no native Excel execution or broader platform certification.

=TIMEVALUE(time_text)

The required argument is text in a recognized Excel time format. Microsoft explicitly illustrates 12-hour text with AM/PM and 24-hour text. The examples here assume English parsing of the displayed strings; they do not certify every regional or imported format.

Format the output as Time for a clock display or Number for its day fraction. If the input is already a numeric Excel time, do not assume reparsing it as text is necessary. Preserve the stored type when that is already the intended value.

=TIMEVALUE("6:30 PM")
=TIMEVALUE("18:30")

Both have expected fraction 37/48, approximately 0.770833333, corresponding to 18:30. Multiplying that fraction by 24 gives 18.5 hours after midnight, not 18.30 decimal hours.

For comparison, =TIMEVALUE("6:30 AM") gives 13/48, approximately 0.270833333. The difference between the two numeric times is 0.5 days, or 12 hours. Omitting the AM/PM distinction would change the intended instant.

Enter the text strings 06:30, 13:15 and 23:45 in A2:A4. Prefix with an apostrophe during entry if needed to prevent automatic conversion; that entry marker is not part of the intended string.

In B2 enter =TIMEVALUE(A2) and fill down. Expected day fractions are approximately 0.270833333, 0.552083333 and 0.989583333. Their exact numerators over 96 are 26, 53 and 95.

Keep the original text and the parsed result in separate columns while checking an import. A clock-like appearance alone does not establish that a cell contains a numeric time usable in arithmetic.

=(TIMEVALUE("17:15")-TIMEVALUE("08:45"))*24

Expected result: 8.5 hours. The day fractions differ by 17/48; multiplying by 24 changes the unit from days to hours. A break duration is not automatically removed: subtract it explicitly if the reporting policy requires it.

For a 30-minute break in this example, subtracting 30/60 gives 8 hours. The function does not infer work rules from the labels Start, End or Break.

Clock times 22:30 and 06:00 have a direct difference of −16.5 hours if no dates are supplied. If the business rule explicitly states that 06:00 is the following morning, use:

=MOD(TIMEVALUE("06:00")-TIMEVALUE("22:30"),1)*24

Expected result: 7.5 hours. MOD converts the negative clock difference into the corresponding interval within one day.

This is not a universal timestamp repair. It cannot distinguish an actual 31.5-hour interval from 7.5 hours, and it can hide a mistakenly reversed same-day pair. Store complete dates when intervals may span more than one day.

Under the stated English parsing scope:

=TIMEVALUE("14-Oct-2026 06:30")
=TIMEVALUE("15-Oct-2026 06:30")

Both have expected result 13/48. Subtracting them gives 0, even though the complete timestamps are one day apart. The equal output is correct for TIMEVALUE’s date-ignoring contract.

For the complete timestamp string in A2, =DATEVALUE(A2)+TIMEVALUE(A2) is a documented-contract composition when both parts are recognized. For October 14 at 06:30, the 1900-system expected serial is approximately 46309.270833333. DATEVALUE contributes the date while TIMEVALUE contributes the time.

The formula does not establish that a timestamp is UTC, apply an offset, or resolve a daylight-saving transition. Strings containing time-zone suffixes and nonstandard duration formats require separately verified parsing rules.

A duration string such as 27:00 is also outside the ordinary one-day clock examples here. If the input means 27 elapsed hours, a numeric quantity 27/24 preserves that duration; a time-of-day parser should not be assumed to preserve complete days.

The dedicated source establishes recognized text formats and ignored date information but does not provide a complete native error table for invalid text, blanks, logical values or numeric arguments. Those outputs are not guessed in this guide.

Use TIME when hour, minute and second components are already known as numbers. Keep parse failures visible rather than replacing them with midnight and making an unresolved input look valid.

• Microsoft TIMEVALUE reference.
• Editorial testing standards.

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.