MODE.MULT in Collabora Office: Multiple Modes and Documented Array Entry

• Introduced: original Collabora release and launch date are not established by the reviewed sources.
• Availability: currently documented in Collabora Office 26.04 desktop help.
• Platform scope: online and mobile deployments are not inferred from this desktop-help release.
• Checked: October 14, 2026. Function-specific documentation and independent calculations; no native Collabora execution.

=MODE.MULT(number1;[number2];...)

The reference permits up to 255 numeric arguments or references. Its dedicated section establishes a vertical output and the array-entry requirement. The examples use semicolon separators and numeric cells.

For the two-result example below, select C2:C3, enter the formula and use the documented array-entry command. In the Function Wizard, mark Array. Direct keyboard entry uses Ctrl+Shift+Enter, with Command+Shift+Enter in the help’s macOS variant. Do not type braces around the formula yourself. See the linked Collabora array-entry instructions.

Enter 2,2,7,7,9 in A2:A6. In the selected C2:C3 output range, enter as an array formula:

=MODE.MULT(A2:A6)

There are two modes: 2 and 7 each occur twice, while 9 occurs once. Expected output is a two-row, one-column array:

This two-value order follows the documented first-result equivalence to MODE.SNGL, whose tie rule chooses the smaller value. It does not establish the complete ordering of larger arrays containing three or more tied modes.

The table headings above explain cell locations; they are not returned cells. Ordinary non-array entry returns only 2, so that single visible value is not proof that 7 failed to tie.

Add 7 in A7 and use a separate one-cell array-formula output for:

=MODE.MULT(A2:A7)

Expected mode is now 7 alone, with three occurrences. The previous two-result output shape no longer describes the new data. This guide does not certify the contents of surplus cells in an oversized result selection.

Determine the intended result range and inspect changed frequencies rather than relying on stale neighboring outputs.

A separate dataset 1,1,4,4,9,9,12 has the mode set {1,4,9}, each occurring twice. The current source establishes a vertical array of modes and the smallest first result through its MODE.SNGL comparison.

The precise order of the other two results is not explicitly specified here. For an audit, compare the returned membership and count against the three expected values instead of certifying a complete three-row order from another spreadsheet.

Group A contains 2,2,7; Group B contains 2,7,7. Their separate single modes are 2 and 7. Pooled data have three occurrences of each, so both values are modes.

Adding 7 to Group B changes the pooled frequencies to three occurrences of 2 and four of 7. Only 7 remains a mode. Keeping just the old group modes would miss this change; retain frequencies or original observations.

For a dataset with no repetitions, the dedicated MODE.MULT section does not give an exact error code. The separately documented MODE.SNGL error cannot automatically be transferred. Text, Boolean, empty-string, source-error and oversized-result behavior also remain unverified.

MODE.SNGL is useful for a deliberately single answer; MODE documents its own range-text rule. Neither a single result nor a formatted display conveys the full frequency distribution.

The source identifies COM.MICROSOFT.MODE.MULT outside the cited OpenFormula 1.3 standard. It does not establish first introduction, native dynamic spilling, or universal file-format interchange.

• Collabora Office 26.04: MODE.MULT.
• Editorial testing standards.

Complete function-specific documentation reviewed. Worked outputs are independent mathematical or explicitly documented rule controls, not application screenshots or native test results. Unresolved ordering, type and error boundaries retain their stated scope.