Contact

PERCENTILE Function in Apple Numbers: Rank Cutoffs and Examples

Statistical Intermediate Apple Numbers

Find percentile cutoffs in Apple Numbers using exact documented arguments, official sample data, and practical interpretation.

Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in Apple Numbers. How formula examples are checked

Quick answer: =PERCENTILE(A1:E4,0.90) returns the value at the 90th percentile of the 20 example scores in Apple’s documentation: 92. PERCENTILE is about a cutoff in a ranked set, not the percentage of cells that satisfy a condition. Apple’s help gives specific results for the same dataset at the 90th, 75th, and 50th percentiles. [A1]

Exact Apple syntax and required arguments

=PERCENTILE(value-set, percentile-value)
Parameter Required? Documented domain
value-set Yes A collection/range containing number, date/time or duration values; all values in that collection must be of the same type.
percentile-value Yes Number from 0 through 1 inclusive. Accepts decimal 0.25, a percent-formatted entry 25%, or an expression evaluating to that number, such as 3/4.

Both arguments are required. There are no optional arguments or default percentile in Apple’s published syntax. Apple says equal values are ranked together and influence the result; do not discard duplicate scores before calculating the cutoff. Its help page does not fully specify the interpolation mechanism for every conceivable data length. For exact intermediate results, rely on its stated examples or run native Numbers validation rather than importing Excel’s algorithm as fact. [A1]

Platform, version, Numbers table references and regional syntax

This tutorial is based on Apple Formulas and Functions Help, documentation edition 15.4, with the function page accessed 2026-10-12. The edition label identifies the help material, not a proven minimum release of Numbers on every device. Apple provides separate release information for Mac; if you must support a particular historical app version, check that release’s availability before deploying this formula. [A1, R1]

All input examples use cells in one Numbers table, with ranges such as B2:B9. Numbers spreadsheets can contain multiple tables on a sheet; when sourcing another table, select its cells through the formula editor so Numbers constructs the table- or sheet-qualified reference. Do not paste Excel’s Sheet!A1 form and assume it means the same thing in Numbers. [R1, R2]

Locale: These formulas use English function names, . for decimal fractions and , between function arguments. If the system uses a comma decimal separator, Apple instructs using semicolons between arguments when formulas are typed manually. Colons identifying ranges, such as B2:B9, stay colons. Function-name capitalization is not significant. [R1]

Verification labels: Documentation-checked expected output means Apple published that exact example. Independently calculated expected output means the mathematical result was checked outside Numbers. Neither is an observation from running Apple Numbers; native Apple Numbers execution and screenshots were not available in this review.

Reproduce Apple’s 20-student example exactly

Create a Numbers table with 5 columns and 4 rows, containing the numeric values below in A1:E4. To avoid header rows changing which row gets the first number, either turn off header rows for this example or create the table initially without one. Keep formulas in another unused column or a separate results table; never put the result in A1:E4.

Row A B C D E
1 30 75 92 86 51
2 83 100 92 68 70
3 77 91 86 85 83
4 77 90 83 75 80
Formula to enter in an empty result cell Documentation-checked expected output
=PERCENTILE(A1:E4,0.90) 92
=PERCENTILE(A1:E4,3/4) 87
=PERCENTILE(A1:E4,0.50) 83

These are the three specific outputs printed in Apple Functions Help 15.4, not results observed from this run in Numbers. The second formula uses 3/4, which evaluates arithmetically to 0.75. If your app locale uses a decimal comma, the first example uses =PERCENTILE(A1:E4;0,90) when typed manually; the slash in 3/4 remains an arithmetic operator. [A1, R1]

What a 90th-percentile result means

In this example, 92 is the 90th-percentile threshold given the 20 scores. It is not 90% of the highest score (0.9 × 100 = 90), and it is not necessarily a score held by exactly 90% of students. Percentiles describe a ranked distribution and can involve ties. A score of 92 occurs more than once in the example, and Apple specifically notes that repeated values influence its percentile calculation. [A1]

The 50th percentile of 83 is also consistent with the central value of the sorted scores; don’t confuse it with the arithmetic mean. For distributions with outliers, median/percentile summaries may tell a different story than AVERAGE.

Advanced: scenario cutoffs and percentile-input cells

Put 0.90 (a numeric value) in a separate cell G2 and reference that cell:

=PERCENTILE(A1:E4,G2)

Expected result: 92, obtained by applying Apple’s documented 90th-percentile example to an equivalent numerical argument. Change G2 to 0.50 and the expected result becomes 83. You can expose that input to an analyst to compare cutoff levels without editing the formula. These two G2 cases are independently reasoned substitutions of Apple-published examples; native execution was not available. [A1, C1]

To represent the top quartile’s lower score threshold, enter =PERCENTILE(A1:E4,0.75); Apple’s 3/4 example documents that this cutoff is 87 for this exact sample. This can be a useful threshold for reviewing high scores, but does not decide which students should receive an award without your policy for ties. [A1]

Percentile and ranking are not interchangeable

PERCENTILE asks which value corresponds to a percentile. Apple’s PERCENTRANK asks a different question: which percentile rank corresponds to a value. Apple’s QUARTILE is another distinct summary function. The help pages are linked below so you can choose the function matching the analytical question. [A1]

Common errors, limitations and troubleshooting

  1. A percent outside 0–100%: percentile-value must satisfy 0 ≤ p ≤ 1. Input 90 is not the same as 90% or 0.90 and violates the documented domain. The exact displayed Numbers error text has not been natively verified. [A1]
  2. Not enough arguments: the set and requested percentile are both required; omitting percentile-value cannot be treated as an implicit median. [A1]
  3. Mixed types: Apple’s collection rule permits numbers, dates or durations but says all collection values must share a type. This tutorial uses numbers; don’t mix test scores with date cells. [A1]
  4. Header accidentally included: in the example, A1:E4 must contain only the 20 numeric entries, with no text header in that rectangle. Move labels outside or disable the header.
  5. Duplicates removed: don’t deduplicate scores: Apple explicitly says tied values affect the result. [A1]
  6. Unexpected decimal/argument separator: for comma-decimal systems use semicolons to separate typed arguments, for example =PERCENTILE(A1:E4;0,90). [R1]
  7. Different result from Excel: Microsoft provides PERCENTILE.INC and PERCENTILE.EXC, separate inclusive and exclusive families. Apple’s help here does not document all interpolation edge cases, so don’t assume either Excel mode is an exact implementation match without comparison tests. [X1]
  8. Small or unusual collection: Apple’s function documentation does not set out all degenerate collection/error behaviors; validate empty and one-item ranges in native Numbers before promising an error code or a boundary output.

Reference access date: 2026-10-12. Apple documentation example outputs were not run in Numbers. C1 is independent arithmetic-equivalence reasoning; native tests were not performed.

Migration and validation limits

The formulas were not executed in a native Numbers app on Mac, iPad, iPhone or iCloud.com. Recheck display formatting, locale entry, data typing, empty/error cells, table references and older release support in the target installation. Test representative examples in the target app before relying on the worksheet. Do not use this tutorial as a substitute for reviewing the data collection method or domain-specific analysis assumptions.