MROUND in Collabora Office: Round to the Nearest Chosen Multiple
Use Collabora MROUND for nearest-step rounding, compare rounding each row with rounding a total, and verify practical interval examples.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: MROUND rounds a value to the nearest multiple of a chosen step. =MROUND(15.5;3) is expected to return 15, because 15.5 is closer to 15 than to 18.
Availability and version history
- Introduced: original Collabora release and launch date are not established by the sources reviewed.
- Availability: documented in Collabora Office 26.04 help, scoped to the desktop-help release.
- Platform scope: support in every online or mobile deployment is not inferred from desktop documentation.
- Checked: October 14, 2026. Complete function-specific documentation and independent arithmetic controls; no native Collabora test was performed.
Syntax and rounding policy
=MROUND(number;multiple)
Both arguments are required. The official reference gives multiple*ROUND(number/multiple) as an alternative calculation. The worked examples below use positive values and positive, nonzero steps, away from exact halfway cases.
English function names and semicolon argument separators are used throughout. A step is a spacing between allowable values, rather than a number of decimal places. For decimal-place rounding, see ROUND.
Example 1: inspect the two neighboring multiples
For a value of 15.5 and a step of 3, the neighboring multiples are 15 and 18. Their distances from 15.5 are 0.5 and 2.5. Therefore:
=MROUND(15.5;3)
Expected result: 15. For the related controls 16.4 and 16.6, the expected results are 15 and 18. The midpoint between those two multiples is 16.5; that exact boundary is deliberately outside these controls.
The nearest result can be smaller or larger than the input. This is not a rule for always buying enough material or always staying below a maximum.
Example 2: round measurements to quarter units
Enter 1.12, 1.14, 1.36 and 1.39 in A2:A5. Enter this formula in B2 and fill down:
=MROUND(A2;0.25)
Expected outputs are 1, 1.25, 1.25 and 1.5. Keep at least two decimal places visible when inspecting the results. Changing the display format alone does not change the stored measurement.
For the second input, compare distances: 1.14 is 0.14 from 1 and 0.11 from 1.25. The latter is the nearer quarter-unit value.
Advanced example: round duration minutes to a scheduling interval
Suppose a model stores elapsed durations as numeric minutes, rather than as clock times. Put 22, 23, 37 and 38 in D2:D5:
=MROUND(D2;15)
Expected rounded durations are 15, 30, 30 and 45 minutes. This example uses minutes consistently for both arguments. Passing a spreadsheet day fraction with a step of 15 would mean a completely different unit.
This is a nearest-interval planning model. If a policy requires every partial interval to count as a full interval, use a separately specified upward-rounding rule instead.
Advanced example: rounding rows and rounding their total differ
Two separate measurements are 1.24 and 1.24, and the step is 0.5:
=MROUND(1.24;0.5)+MROUND(1.24;0.5)
=MROUND(1.24+1.24;0.5)
Expected results are 2 and 2.5. The first calculation rounds each measurement to 1 before adding. The second adds the unrounded measurements to 2.48 before rounding.
Neither ordering is automatically correct for every workbook. Write down whether the policy applies to each line or to the combined quantity, and retain that distinction when subtotals are added.
Independent check and limits
=0.25*ROUND(1.39/0.25)
The expected result is 1.5, matching the quarter-unit example. This follows the alternative expression printed in Collabora’s own reference.
The short MROUND section does not establish a complete signed-input, zero-step, exact-midpoint or floating-point boundary matrix. Those native cases remain unverified here. In particular, do not import another product’s sign restrictions or midpoint error examples into this guide.
References and verification
The complete function section was reviewed. Worked results are independently checked expectations; native execution and unlisted edge cases remain unverified.