MINUTE in Google Sheets: Extract Clock Minutes and Build Quarter-Hour Buckets

• Introduced: first introduction date is not established by the official history reviewed; no desktop release number is inferred.
• Availability: documented in the rolling Google Sheets service; these examples use the web worksheet workflow.
• Checked: October 14, 2026; official MINUTE reference. Documentation and independent models, with no native Google Sheets execution or wider client certification.

=MINUTE(time)

Use a date-time cell, TIME expression or suitable numeric serial. Google describes an integer component and notes that a DATE-only value has a midnight time portion.

The help page has a quoted-time sample alongside cautionary parsing notes. These examples avoid that ambiguity by constructing numeric times. Do not place a bare colon expression such as 12:00:00 directly in the argument and expect it to behave like a time entered into a cell.

=MINUTE(TIME(2,45,30))
=MINUTE(TIME(2,59,59))
=MINUTE(TIME(3,0,0))

Expected results are 45, 59 and 0. The last result resets because the clock has entered another hour. It does not say no minutes have elapsed since the earlier timestamp.

Keep the output as a number. A time format applied to the integer 45 does not reconstruct 02:45:30; the original hour and second components have already been omitted.

=MINUTE(TIME(8,15,0))
=MINUTE(TIME(19,15,0))
=MINUTE(DATE(2026,10,14))

Expected values are 15, 15 and 0. The two clock times differ by 11 hours, or 660 minutes, despite sharing the same extracted minute. The date-only control returns the midnight minute component.

When an event’s date and hour matter, retain the full timestamp rather than grouping only by MINUTE.

For times within an hour, put minute components 0, 14, 15, 29, 30, 44, 45 and 59 in B2:B9. Create each A-row time with =TIME(8,B2,0), then fill down:

=INT(MINUTE(A2)/15)

Expected bucket numbers are 0, 0, 1, 1, 2, 2, 3 and 3. The bins represent minutes 0–14, 15–29, 30–44 and 45–59 under the stated whole-minute controls.

This is a grouping rule, not rounding to the nearest quarter hour. A time at 08:14 stays in the first bin rather than moving to 08:15.

For A2 containing =TIME(8,37,20):

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

Expected result: 08:30:00. The minute component is 37, the bucket index is 2, and 15×2 gives the bucket’s starting minute 30. Seconds are deliberately set to zero.

This formula returns only a clock value. If records from multiple dates are grouped together, retain a separate date key or deliberately rebuild the full bucket timestamp; otherwise unrelated mornings can be merged.

For whole-second timestamps, use:

=AND(MOD(MINUTE(A2),15)=0,SECOND(A2)=0)

The inputs 08:15:00, 08:15:30, 08:30:00 and 08:31:00 produce expected flags TRUE, FALSE, TRUE and FALSE. A minute-only test would wrongly admit 08:15:30 under an exact-boundary requirement.

The rule is limited to the whole-second fixture. It does not establish how SECOND treats every fractional-second timestamp.

With start D2 at October 14, 2026 08:00 and end E2 at October 15, 2026 10:30, both built from DATE plus TIME:

=MINUTE(E2)-MINUTE(D2)
=1440*(E2-D2)

Expected results are 30 and 1590. The second retains the full 26.5-hour interval. A plain subtraction of minute components loses the completed day and hours.

For a time-only value =TIME(2,45,30), multiplying its day fraction by 1440 gives 165.5 minutes since midnight, while MINUTE remains 45. Those two calculations answer different questions even before dates are involved.

The dedicated reference does not specify a complete numeric/text/blank error matrix, serial range or fractional-second rounding rule. No matching Excel error behavior is assumed. Numeric controls here are independently modeled, and imported timestamp strings need their own recognition checks.

Use TIMEVALUE to parse recognized time text, TIME to build numeric components, and HOUR or SECOND for the adjacent clock components.

• Google MINUTE reference.
• Editorial testing standards.

Examples use fictional inputs, English function names and comma argument separators. Expected outputs are independently modeled from the cited rules, not native Sheets captures. Check the spreadsheet locale when reproducing punctuation-sensitive formulas.