MINUTE in Collabora Office Calc: Extract Minute Components and Build Time Buckets

• 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.

=MINUTE(number)

The argument is a numeric internal time value. The Collabora reference says the integer part of the minute is returned and supplies fractional-day examples that retain a minute component within the hour.

Use a plain-number format for the result. MINUTE does not create a new clock time and does not calculate a duration by itself.

=MINUTE(TIME(9;0;0))
=MINUTE(TIME(9;45;30))
=MINUTE(TIME(23;59;59))

Expected results are 0, 45 and 59. The seconds 30 in the middle control do not turn the result into 45.5. The component remains an integer.

For 09:45:30, the independent total-minute calculation is 9×60+45+30/60=585.5. That larger quantity uses the hour and seconds too.

=MINUTE(8.999)
=MINUTE(8.9999)

The direct source gives expected results 58 and 59. The integer 8 represents whole days; the fractional parts specify times within a day.

Mathematically, 0.999 day corresponds to 23:58:33.6, while 0.9999 day corresponds to 23:59:51.36. Extracting the integer minute gives the documented answers. These controls show why reading the decimal digits as an HH.MM notation is incorrect.

A duration of 90 minutes is 90/1440 of a day:

=MINUTE(90/1440)
=(90/1440)*1440

Expected results are 30 and 90. The first is the minute within the 1:30 clock representation; the second converts the complete day quantity to minutes.

If a report asks for total elapsed minutes, using MINUTE discards the hours. Multiply a valid duration by 1440 and preserve the duration’s sign and day context instead.

Enter 09:07:00, 09:15:00, 09:29:00 and 09:59:00 in A2:A5 using TIME. In B2 enter and fill down:

=TIME(HOUR(A2);15*INT(MINUTE(A2)/15);0)

Expected clock values are 09:00:00, 09:15:00, 09:15:00 and 09:45:00. The minute component is divided by 15, INT selects the lower bucket, and multiplying by 15 restores its minute boundary.

This is an explicitly chosen rounding-down policy. It does not round to the nearest quarter hour. The expression also returns a time-only value; a source timestamp’s date must be retained separately if the output needs it.

For the 09:29 control, subtracting the bucket 09:15 leaves 14 minutes. For 09:59, the difference from 09:45 is also 14 minutes. Multiply the time-fraction difference by 1440 to express that quantity numerically.

At the exact boundary 09:15, the removed time is zero. Test an exact boundary along with an interior case so an off-by-one bucket rule does not go unnoticed.

For A2=TIME(9;45;30):

=HOUR(A2)*60+MINUTE(A2)+SECOND(A2)/60

Expected result: 585.5 minutes since midnight. The whole-second controls make the reconstruction explicit. Collabora’s SECOND uses nearest-second rounding, so this expression is not guaranteed to retain an original subsecond fraction.

Keep numeric time values separate from time-like text. The selected reference does not establish every parsing, blank, negative-time or native error case, and no such rule is borrowed from another program.

Neither a minute component nor a day fraction encodes a timezone. A local-clock label must not be treated as a universal instant without additional information. See HOUR, SECOND and TIME for their different operations.

• Collabora Office 26.04: MINUTE.
• 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.