MODE in Collabora Office: Most Frequent Values, Ties and Numeric Range Labels
Find Collabora MODE with a frequency table, verify the smallest-value tie rule, and distinguish a mode from a majority.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: MODE returns the most frequent value in a dataset. Collabora explicitly resolves tied frequencies by returning the smallest tied value. A most-frequent value does not have to appear in a majority of the rows.
Availability and version history
- 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.
Syntax and documented inclusion
=MODE(argument1;[argument2];...)
The current help permits up to 255 arguments and ignores text and empty cells inside data ranges. It says an error occurs when no value appears twice, but this MODE section does not identify the exact displayed error code.
The examples use numeric categories, English function names and semicolon separators. A numeric category can have a mode even when adding or averaging the category codes would not make practical sense.
Example 1: audit a tied frequency table
Enter 2,4,4,7,7,9 in A2:A7:
=MODE(A2:A7)
Expected result: 4. The complete frequencies are:
| Value | Occurrences |
|---|---|
| 2 | 1 |
| 4 | 2 |
| 7 | 2 |
| 9 | 1 |
Both 4 and 7 occur twice. The documented smallest-value tie rule selects 4. Neither occurs more than three times, so neither is a majority of the six observations.
Example 2: one more observation changes the winner
Put 7 in A8:
=MODE(A2:A8)
Expected result: 7, now occurring three times against two occurrences of 4. Its share is 3/7, approximately 42.857143%, still below a majority.
The change from 4 to 7 reflects a frequency change. It is not caused by 7 being numerically larger; when frequencies were tied, the smaller value won.
Advanced example: ordering and tie identity
In C2:C7 enter the original values in reverse order: 9,7,7,4,4,2. Expected MODE remains 4. The winning tie is determined by the smallest tied value, rather than whichever tied value happens to occur first in this reordered list.
For -3,-3,2,2,5, both -3 and 2 occur twice, so expected MODE is -3. “Smallest” means numerical order, not the smallest absolute magnitude.
If every original record is duplicated, the frequency table becomes 2,4,4,2 across the four distinct values. The same 4-versus-7 tie persists and MODE remains 4. Retain a separate record count if duplicate records would invalidate the analysis.
Advanced example: display rounding is a separate operation
Put 1.21,1.22,1.21 in E2:E4. These numeric values have mode 1.21, because it appears twice. If all three cells merely display one decimal place, their underlying values have not thereby become identical.
If you explicitly transform each with =ROUND(E2;1) and fill a separate helper dataset, those three inputs become 1.2,1.2,1.2 and its mode is 1.2. Decide whether the question concerns original measurements or explicitly rounded categories, and keep the transformation visible.
Labels, no repetition and related functions
Extending the original range with text Pending and a genuinely empty cell retains expected MODE 4 under the documented exclusion rule. A range consisting of the distinct numeric values 2,4,7,9 instead reaches the documented no-repetition error; this guide leaves its exact MODE code unverified.
MODE.MULT returns the multiple-mode result array, while MODE.SNGL has its own single-result section and separately documented error wording. Do not transfer every type or error rule between spellings.
MODE remains documented in Collabora 26.04. The source’s OpenDocument 1.2 standards note does not establish its first Collabora release or a retirement date. Direct text, Boolean, formula-empty and source-error behavior remain outside the verified range-text rule.
References and verification
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.