PlanMaker MINUTE Function: Syntax and Verified Time Examples

• Introduced: Documented by PlanMaker 2021; the original introduction version is not established.
• Availability: Documented in PlanMaker 2026. This is a supported-version reference, not a final working-version endpoint.
• Scope: The reference belongs to the 2026/NX manual family; availability in FreeOffice and individual mobile builds is not established here.
• Checked: October 14, 2026, against the official function reference. Documentation check; not a new native test.

Use MINUTE when an arrival log must display a minute-within-hour field, a clock-scheduled process must match :15 or :45, or you want to check that a timestamp is on a five-minute boundary. Keep the actual time-valued cell for chronological sorting and accurate durations.

=MINUTE(Time)

There is exactly one argument, so no argument-order ambiguity and no optional arguments or defaults. A cell reference such as A3 is not quoted; a text literal such as "12:34:56 AM" is quoted. The latter requires locale-aware parsing. This function does not accept separate hour, minute and second parameters—that is what the constructor TIME(Hour,Minute,Second) is for. The English manual uses comma-separated arguments for TIME; an installation may use a different formula-list separator depending on its settings. Official function page; TIME constructor.

PlanMaker stores times as numerical fractions of a day. To avoid ambiguous date strings, enter the formulas in column A below. The constructor TIME(Hour,Minute,Second) is described in SoftMaker’s TIME reference. Formula names and commas follow SoftMaker’s English documentation; if your installation uses semicolons for arguments, replace the separators accordingly. The displayed format may vary independently of the stored fraction. Format A2:A6 as hh:mm:ss if necessary. Do not type the visible time as a string.

Validation label: The component values above were independently calculated from 24-hour clock arithmetic with Python’s datetime.time; they are expected outputs, not observed PlanMaker results. Each constituent function is documented separately, but this complete sheet has not been opened in PlanMaker. If a locale uses another time display or formula separator, adapt presentation or separators rather than changing the intended numeric times. SoftMaker time entry documentation.

Enter =MINUTE(A2) into B2 and fill through B6. The independently expected sequence is 0, 45, 30, 5, 59. SoftMaker separately documents MINUTE("12:34:56 AM") returning 34, and MINUTE("09/25/2018 10:30:56 AM") returning 30. Those two values are documented examples, not PlanMaker execution results from this batch.

Advanced: five-minute schedule validation

For inputs known to have whole-second precision, check a five-minute boundary with =AND(MOD(MINUTE(A3),5)=0,SECOND(A3)=0). For A3=06:45:12, the expected answer is FALSE because the seconds component is 12, even though 45 is divisible by 5. For a clean time TIME(6,45,0) the expected answer is TRUE. This combines three documented functions with independent integer reasoning; native behavior has not been observed.

Advanced: calculate an elapsed 95 minutes

Put =TIME(9,15,0) in D2 and =TIME(10,50,0) in E2. The difference is mathematically 95 minutes. =MINUTE(E2-D2) only asks for the minute component of that duration, expected 35; it discards the complete hour. =ROUND((E2-D2)*1440,0) is independently expected to return 95, where 1440 is 24 hours × 60 minutes. For overnight intervals, use full date/time values or explicitly account for the calendar day; the example assumes both entries are the same day.

A cell with a displayed time 10:50 might have underlying seconds not visible because of formatting. If exact scheduling matters, check SECOND as well before classifying a row.

For =TIME(18,5,9), MINUTE(...) extracts 5, not the 1085 full minutes from midnight (18×60+5). If the time serial has no date portion, the mathematical full-minute count is (time-INT(time))*1440; this expression is a calculation method, not the documented meaning of MINUTE, and any fractional seconds can make it non-integral. Use ROUND, INT or an explicit rounding rule only after deciding whether precision should be truncated, rounded or preserved.

Important uncertainty: The brief function page does not supply a complete matrix of conversion/overflow/error-code rules. No #VALUE!, #NUM!, precision threshold or input coercion is promised without application execution. Regional parsing, saved file formats and the numeric time’s stored precision deserve manual testing.

Excel also documents MINUTE(serial_number), returning an integer 0 through 59. PlanMaker 2021, 2024 and 2026 show the same one-argument English function syntax with a parameter named Time. This establishes comparable purpose, not identical treatment of text literals, locales, early dates or every error. Test imported .xlsx time data with real stored time values rather than assuming formatting means the values are numerically equivalent.

Official reference pages checked 2026-10-12 (UTC): PlanMaker 2026 MINUTE, PlanMaker 2024 MINUTE, and PlanMaker 2021 MINUTE. The syntax printed on these three English manuals agrees. These are documentation checks, not proof that every installation and edition executes identical edge cases. More information: TIME constructor; regional cell entry; custom number formats. Excel MINUTE reference was consulted as an interoperability reference, not a native test.

For adjacent components, refer to the official HOUR, MINUTE, SECOND and MILLISECONDS pages.

Verification summary: Official documentation and independent arithmetic were checked. Native PlanMaker and Excel execution, platform/edition behavior and workbook exchange remain untested.