MODE Function in Apple Numbers: Most Frequent Value, Ties and Errors

=MODE(value, value…)

Apple’s MODE function reference allows date/time and duration values only when they are not mixed with other value types. If either date/time or duration values are included, all values must be of the same value type. This tutorial uses numbers only so it does not need to infer date/time equality or duration display rules. Apple’s documentation does not list a case-sensitivity or weighting argument.

Difference from GEOMEAN/HARMEAN: MODE explicitly permits a collection, so a reference like B2:B6 is supported by its documented input type. This distinction is important when copying formulas from other spreadsheet products.

Create a table named Orders. Make a numeric column B and enter exactly these five records. Put your formula in D2 within that same table.

=MODE(B2:B6)

Expected result from independent frequency counting, and from Apple’s documented tie rule: 6. Both 6 and 2 appear twice; 4 appears once. Because 6 appears before 2 in the input range, MODE selects 6.

If the order is reversed, use a new column with values 2, 2, 4, 6, 6 or test the direct argument form:

=MODE(2,2,4,6,6)

Expected result: 2. Apple’s reference provides this very example. The frequency distribution is the same, but the first tied observation changed; therefore the reported mode changed. If a dataset has ties, a MODE result can change after sorting rows even though the underlying multiset of values stays the same.

1. Distinguish a unique winner from tied winners

For a simple dataset with a unique most frequent value, enter values 7, 4, 7, 7, 9 into B2 through B6 and use:

=MODE(B2:B6)

Independently counted expected result: 7. The frequencies are 7 → 3, 4 → 1, 9 → 1. Because 7 alone has the highest frequency, input order no longer changes which numeric value is returned.

If you are preparing a management report where ties must be disclosed, MODE alone is insufficient. Consider creating a count table using each candidate value and COUNTIF. For instance, with candidate 7 in D2 and the original five input values in B2:B6:

=COUNTIF(B2:B6,D2)

Independently counted expected result: 3 for the unique-mode example. Compare counts for each distinct candidate before stating there is one unique mode. This is a frequency-analysis method; it does not replace checking the input data.

2. All values different: an error, not a mean

=MODE(1,2,3,4,5)

Apple explicitly documents that an error is returned when no value occurs more than once. The existence of an error is documentation-checked; its precise displayed error token was not verified in native Numbers, so it is deliberately not labeled #N/A or any other unsupported token.

A dataset can therefore be perfectly valid for AVERAGE and MEDIAN but not have any repeated value for MODE. In that situation, do not replace the error with zero, which would falsely imply that zero is the modal observation.

3. Context: why the median differs

On the original Orders sequence 6, 6, 4, 2, 2, an independent sort gives 2, 2, 4, 6, 6. Thus:

=MEDIAN(B2:B6)

has expected result 4, while MODE has expected result 6 because of the tie/first-seen rule. Their different answers summarize different aspects of the same data. =AVERAGE(B2:B6) also has expected result 4, because (6 + 6 + 4 + 2 + 2) ÷ 5 = 4. Coinciding AVERAGE and MEDIAN results do not make them the same statistic.

4. Durations and dates: keep types homogeneous

Apple’s signature allows a collection of dates/times or a collection of durations. It explicitly says not to mix date/time with other types or durations with other types. If summarizing most frequent service durations, keep the input column consistently formatted as duration values and validate in the installed Numbers version before using the result in a dashboard. This guide does not invent test outputs for mixed types or assumed date/time internal representations.

• No repeated value: Apple’s official MODE note says this yields an error. Re-evaluate whether you need a central-tendency measure such as MEDIAN instead, but don’t conceal the data fact of no duplicates.
• Ties at maximum frequency: MODE returns the first tied value. Sorting rows can change the selected mode; document ordering or report all ties through a separate frequency table.
• Input is text labels rather than numbers: MODE’s documented supported types are number, date/time and duration. Use counts of categories for text labels instead of assuming the function treats arbitrary strings as modal values.
• Mixed date/time and duration types: Not allowed by Apple’s stated rule; normalize values into a consistent eligible type or work from separate columns.
• Range missing new rows: If new observations are appended below B6, confirm the referenced range includes them.
• Direct arguments versus collection: MODE(5,5,6) and MODE(B2:B4) use distinct syntactic forms. When using a collection, ensure it contains the intended numeric data rather than headings.
• Blank, Boolean or error cells: The short MODE help page does not establish every coercion or skip rule for those values. Inspect the data first; do not assert that arbitrary nonnumeric types are ignored or converted without documentation/native tests.
• Parser or regional separator problem: The English help uses commas between arguments; Apple instructs users with a comma decimal separator to use semicolons for typed multiargument formulas.
• Unexpected modal value after sorting: Test the relative input order of tied values before assuming the calculation is wrong.

Other spreadsheet apps provide mode or most-common-number functionality, but do not assume identical tie breaking, mixed-type handling, error tokens, or variant names without testing the destination product. Excel uses names such as MODE.SNGL in some versions, which is an Excel identifier rather than proof of an Apple Numbers alias. Apple’s documented canonical name here is MODE, and MODE.SNGL is not asserted here as an Apple alias.

Cross-table references also differ: build Numbers’ Table::Cell formula references by selecting cells instead of copying Excel’s Sheet1! syntax. This helps avoid broken formulas in converted spreadsheets.

• MEDIAN — middle ordered value, including even-length data.
• AVERAGE — arithmetic mean, a different notion of typical.
• COUNTIF — count occurrences for a frequency comparison.

This page was researched using the Apple Formulas and Functions Help, edition 15.4, accessed 2026-10-12 UTC. This edition does not by itself prove compatibility with every historical Numbers release or every platform. Not executed in Apple Numbers on macOS, iPhone, iPad, or iCloud.com. The displayed answers below are mathematical or documentation-checked expected results, not screenshots or observed output.

The English help examples separate arguments with commas. Apple documents that regions using a comma decimal separator use a semicolon between arguments typed by hand: see Functions overview. Use the Numbers formula editor to construct references. In another table Numbers uses qualifiers such as Data::B2, not Excel-style Sheet1!B2; see Apple’s argument types and table-reference guidance. Regional number displays can differ without changing the underlying mathematics.

The first-supported Numbers version and older-platform differences were not verified for this function. Do not assume a version simply because the current documentation is edition 15.4.

Official claim sources, checked 2026-10-12 UTC:

• Apple MODE function help, documented as edition 15.4 and accessible Apple function article: function signature, input requirements, and function-specific notes.
• Apple Functions overview: syntax notation and localized argument separators.
• Apple Types of arguments and values: number/collection distinction and Numbers table-qualified references.

Validation: Official documentation and independent arithmetic only; no native Numbers execution or screenshots.