MODE.MULT Function (Gnumeric)

• Introduction: Gnumeric 1.12.23. NEWS explicitly adds MODE.MULT.
• Source support: Registered in the Gnumeric 1.12.62 plugin. No retirement is established. The last functioning application version is unverified for this guide.
• Evidence dates: Official Gnumeric source was retained October 13–14, 2026 and reviewed October 15. The GOffice 0.10.61 source archive was retrieved October 15 and its relevant range routine reviewed the same day. Typed filtering, exact counting and rational interpolation checks are independent reference calculations. No native Gnumeric, compiled-library, headless application or GUI execution was performed.

=MODE.MULT(number1,number2,...)

Arguments may provide numeric values or ranges. The collector ignores strings, Boolean values and physically empty cells. Input errors propagate. The function finds the largest occurrence count, then returns every distinct numeric value having that count.

At least one numeric value must repeat. If there are no duplicates, or fewer than two collected numeric values, the result is #N/A. It does not return all unique observations as tied modes of frequency one. A real zero can be a mode when repeated; it is not an automatic fallback for an empty or unique-only dataset.

The result is a one-column array sorted in ascending numeric order. A list of modes is not a list of their frequencies. Keep a separate frequency calculation if the number of occurrences is needed alongside each value.

Create TiedModes. Put numeric 4,2,4,2,9,9,7 in A2:A8. Select D2:D4 and enter =MODE.MULT(A2:A8) with Ctrl+Shift+Enter, following the pinned Gnumeric array-entry manual.

The value 7 occurs only once and is excluded. The first observed value was 4, but the output starts with 2 because the result is sorted. The worksheet intentionally reserves three result cells because this fixture has three tied modes.

For a changed-input control, replace the final 7 with 9 in a copy. Nine now occurs three times and the only mode is 9. Re-enter the test in a fresh output area sized for that one-value result rather than assuming the original array region resizes automatically. Native spill and excess-output-cell behavior are not certified here.

The outputs are independent frequency-count results matched against the source algorithm. Bracketed lists describe values in cells, not a claim about localized array-literal punctuation. These controls include a tie, a single repeated value, no duplicates, zero and negative modes.

In the original dataset, the sorted observations are 2,2,4,4,7,9,9. Their median is 4, while the modes are 2,4,9. These are different summaries: the median describes central position and the modes describe repeated exact values.

Do not average the modes and call that the mode of the data. The average of 2,4 and 9 is 5, which does not appear among the observations. Selecting the lowest mode is also a separate tie-breaking rule, not the full MODE.MULT result.

When numeric codes represent categories, repeated codes can be meaningful even when their arithmetic mean is not. Keep the code-to-label mapping separate and preserve all ties when the task asks for the most common categories.

Append text 9, Boolean TRUE and a physically empty cell below the original observations, then include those cells in the range. The modes remain 2,4,9 because those appended values are ignored. If the text 9 is replaced by numeric 9, the mode becomes 9 alone.

This distinction matters after imports: a column can look numeric while containing text. Formatting a cell like a number does not by itself establish the stored type. Review the raw data rather than assuming that a discrepancy proves the frequency algorithm is wrong.

The function groups numeric values, not rounded display labels. A workbook that intends bins such as whole units should create a deliberately rounded or classified helper column first. That transformation changes the dataset and should be recorded; MODE.MULT does not silently choose a rounding policy.

For continuous measurements with few exact duplicates, FREQUENCY can count chosen intervals. The interval with the largest count is a modal interval under those chosen bins; it is not an exact MODE.MULT result. Different boundaries can produce different modal intervals without changing the underlying measurements.

Keep exact-value mode and grouped-frequency analysis separate. The absence of a MODE.MULT duplicate result does not imply that the data have no concentration or structure; it only says that no collected numeric value repeats under this function’s rule.

Use #N/A as a diagnostic for the no-duplicate case instead of replacing it silently with zero. An upstream error propagates through numeric collection; it is not treated as another category. Text and Booleans are ignored even when directly supplied as arguments in this implementation.

If only one result is visible, check the array entry and output range. If expected duplicates are missing, inspect data types and full stored precision. If a mode changes after editing one cell, recount every tied value: changing the maximum frequency can remove several former modes at once.

The numerical ordering, collector flags and failure rules are source-backed. Native rendering, localized input coercion, array padding and export round trips remain unverified.

• Function help and worksheet callback
• Numeric collection flags and iteration
• Gnumeric array-entry manual source
• Gnumeric official function catalogue

MODE, MEDIAN, FREQUENCY.