TIME in Collabora Office Calc: Construct a Time from Hours, Minutes and Seconds

• Introduced: original Collabora release and launch date are not established by the sources reviewed.
• Availability: documented in Collabora Office 26.04 help, scoped to that desktop-help release.
• Platform scope: separately deployed Online and mobile versions are not inferred from desktop documentation.
• Checked: October 14, 2026. Direct documentation and independent calendar/time controls; no native Collabora test was performed.

=TIME(hour;minute;second)

All three integer components are supplied. The direct page explains conversion from those components to a decimal time value and demonstrates ordinary times. These examples stay within hours 0–23 and minutes/seconds 0–59; overflow, negative components and fractional component conversion remain unverified.

Despite the word current in the source’s opening sentence, the function constructs the supplied components. It is not the no-argument NOW function for reading the current date and time. Fixed component inputs support reproducible controls.

=TIME(0;0;0)
=TIME(4;20;4)
=TIME(12;0;0)

Expected clock displays are 00:00:00, 04:20:04 and 12:00:00. The first two are explicit examples in the Collabora reference; the third is noon.

Under the documented day-fraction model, their numeric values are 0, approximately 0.180601852, and 0.5. Apply a time format to see the clock components or a number format to inspect the fraction.

Enter numeric 9, 30 and 0 in A2:C2, with Hour, Minute and Second headings. In D2 use:

=TIME(A2;B2;C2)

Expected display: 09:30:00. The time contains 9.5 decimal hours, so the independent fraction is 9.5/24, approximately 0.395833333.

The numeric representation 9.5 hours is different from the text 09:30. Keep the unit in a heading if multiplying the time fraction by 24 for a decimal-hours report.

=DATE(2026;10;14)+TIME(9;30;0)

Expected displayed timestamp: 14 October 2026 at 09:30:00. DATE supplies the whole-day component; TIME supplies the fractional component.

The resulting numeric value does not encode a timezone. It does not prove whether the clock time was recorded in UTC, a local zone or another convention. Preserve that information separately when the source data requires it.

For a start of 09:30 and an end of 17:00 on the same specified date:

=(TIME(17;0;0)-TIME(9;30;0))*24

Expected duration: 7.5 hours. The raw subtraction is 0.3125 days; multiplying by 24 changes the unit.

If the end is on another date, use full DATE+TIME values rather than assuming two time-only values contain that date relationship. TIME provides a clock value, not a complete elapsed-time history.

=((DATE(2026;10;15)+TIME(1;15;0))-(DATE(2026;10;14)+TIME(22;45;0)))*24

Expected duration: 2.5 hours. The start and end dates make the overnight relationship explicit. Subtracting only 01:15 minus 22:45 would instead give a negative 21.5-hour difference.

Adding a day automatically whenever a time difference is negative would be a separate policy that can hide reversed records. Keep the actual dates when they are known.

For D2 containing the original 09:30 time:

=TIME(HOUR(D2);MINUTE(D2);SECOND(D2))

The expected reconstructed clock time is 09:30:00 for this whole-second control. This is not a general lossless transformation for fractional seconds: Collabora’s SECOND explicitly rounds to a nearest second.

Check whether the output is date/time-formatted or shown as a fraction before changing a correct formula. Use TIMEVALUE for a valid textual time rather than assuming TIME’s numeric arguments parse every imported string.

The selected reference does not establish every invalid input, 24-hour overflow or current deployment’s error labels. No native runtime, timezone transformation or universal duration-format behavior is claimed here.

• Collabora Office 26.04: TIME.
• Collabora date/time model and date bases.
• Editorial testing standards.

The dedicated product help was read directly. Calendar and numeric outputs are independently calculated expectations, with stated parsing and boundary limits. No native runtime or universal cross-deployment certification is claimed.