MODE.SNGL in Collabora Office: Single Modes, Smallest Ties and the No-Duplicate Error

• 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.SNGL(number1;[number2];...)

Collabora allows up to 255 numeric arguments, cell references or ranges. The compact dedicated section does not supply the range-text exclusion note found on MODE, so this guide uses numeric data rather than assuming identical mixed-type conversions.

One returned value does not show whether other values tied for first place. A frequency table or MODE.MULT is useful when that distinction matters.

Enter 10,10,15,15,20 in A2:A6:

=MODE.SNGL(A2:A6)

Expected result: 10. Both 10 and 15 appear twice, while 20 appears once. The smallest-value rule selects 10.

Rearrange those same values as 15,15,20,10,10 in C2:C6. Expected result remains 10 even though 15 appears first. The order of records is separate from the documented numerical tie rule.

Add another 15 in A7:

=MODE.SNGL(A2:A7)

Expected result: 15, now occurring three times. Its frequency is 3/6, exactly one half, rather than more than one half. The mode is the most frequent value, not necessarily a strict majority.

For -4,-4,1,1,8, the tied winner is -4. Taking absolute values before finding a mode would change the dataset and is not part of MODE.SNGL.

Put 10,15,20 in E2:E4:

=MODE.SNGL(E2:E4)

The Collabora reference explicitly specifies #VALUE! for this no-duplicate case. This is a documentation-based expected result, not a captured native run. Another spreadsheet’s differently named or similarly named function may document a different error.

Returning zero as a fallback would hide the absence of a repeated value and invent a category not present in these data. Keep the no-mode condition visible in a report.

Consider two groups:

• Group A: 1,1,2, with mode 1.
• Group B: 2,2,2,3, with mode 2.

The combined observations are 1,1,2,2,2,2,3. Their mode is 2, with four occurrences. Averaging the group modes would give 1.5, a value absent from every original record.

Even retaining only the two group modes loses the frequency information needed for general pooling. Keep counts for each category or the original observations; group size alone is not always enough.

Values 1.21,1.22,1.21 have expected mode 1.21. Rounding each value to one decimal first creates 1.2,1.2,1.2 and gives mode 1.2. A display format alone is not that explicit data transformation.

Document which precision defines an observation or category before interpreting a repeated-value result. Preserve the original measurements alongside any rounded helper range.

The source names COM.MICROSOFT.MODE.SNGL and places it outside the cited OpenFormula 1.3 standard. This is a formula-format note, not proof of universal export compatibility or unavailability in Collabora.

MODE remains currently documented as a separate spelling. No first release or retirement is established here. Text, Boolean, formula-empty and source-error inputs remain unverified for MODE.SNGL rather than borrowed from another section.

• Collabora Office 26.04: MODE.SNGL.
• 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.