RANK.EQ in ONLYOFFICE: Ranking Direction and Equal Values

Use RANK.EQ in ONLYOFFICE to assign an observation its position in a numeric list, giving tied values the same best position. The working example below describes delivery lead times; it returns a position, not hours. The official reference supports the function’s identity and purpose.

This guide separates documentation review from application testing. The expected numbers are independently calculated, not screenshots or results captured from ONLYOFFICE.

RANK.EQ(number, ref, [order])

Value: the measurement whose rank is required, here an observation already present in the register.

Reference range: the comparison group. Lock its row and column coordinates when copying a ranking formula.

Direction: descending for highest-first ranking, ascending for lowest-first ranking. The examples state the direction explicitly and use the parameter form documented for this program.

Use RANK.EQ when every row needs a position against the same comparison group. Unlike LARGE or SMALL, which return a value when given a position, ranking starts with a value and returns its position. Keep an ordinary record identifier as well; a rank is not a stable ID.

The EQ tie rule is competition ranking: if two records share second place, both receive 2 and the next record receives 4. It is neither average ranking nor dense ranking. A leaderboard that must award a unique position to every row needs a separate, documented tie-break rule rather than an assumption that this function resolves ties.

A team delivery register with one row per completed shipment provides the scenario. Enter the following numeric observations into A2:A9, one per row, with a header in A1. Use a spare result cell outside the input range.

Download the ONLYOFFICE RANK.EQ practice data (CSV). Import it into a new, blank sheet starting at A1, with a comma as the file delimiter and the header row retained. The CSV contains input values only, not formulas or native test results. Blank spacer columns place the requested position in D2 and any additional test data in column F. Keep observations numeric rather than importing them as text.

Example 1: Rank a row with the highest value first

=RANK.EQ(A2,$A$2:$A$9,0)

Expected result: 7.

A2 contains 14. There are 6 observations greater than 14, so its descending position is one plus that count. The reference range stays fixed when this formula is copied down.

Example 2: Make the equal-value rule explicit

=RANK.EQ(18,A2:A9,0)

Expected result: 5.

The value 18 occurs 2 times. Each occurrence receives rank 5; a lower distinct value follows those tied positions rather than receiving the next dense rank. Duplicate measurements remain separate observations.

Example 3: Switch to lowest-value-first ranking

=RANK.EQ(A2,$A$2:$A$9,1)

Expected result: 2.

The nonzero/true direction switches to ascending order. There are 1 observations below 14, so its ascending rank is one plus that count. Choose this direction when a lower measurement should receive rank 1.

For a value present in the list, descending rank equals one plus the count of observations strictly greater than it. Ascending rank uses the count strictly below it. This explains equal ranks without choosing a particular tied row or sorting only part of a record. Keep stored results at full available precision and round only the final presentation when a report requires it. The displayed expectations above are rounded where necessary; a different number of displayed decimal places is not by itself a calculation error.

There are gaps after a tie. That is the intended best-position rule, not a missing result. Do not renumber the remaining rows unless your report deliberately uses a different ranking scheme.

The apparent best record ranks last. Check the direction. Descending order gives the highest number rank 1; ascending order gives the lowest number rank 1. Use an explicit direction in shared workbooks instead of leaving the interpretation implicit.

Displayed values look tied but ranks differ. Formatting can hide differences in the underlying numbers. Decide whether the ranking rule should use full precision or deliberately rounded measurements, then create the intended numeric input before ranking. Keep the comparison range fixed when copying down.

The ONLYOFFICE function page supplies the software-specific reference. The documented worksheet form works with numeric values and cell ranges. The examples do not require a separate analysis plug-in, array-spill result or macro.

In the delivery-register example, decide whether the measurement includes weekends, transit time only or the complete time from order to delivery. These are different variables even when their cells are all formatted as hours. Do not mix them in a single range and expect a dispersion or ranking formula to reconcile the definitions.

When reviewing a shared document, keep measurement cells apart from commentary and summary rows. A plain numeric range makes it easier for another editor to audit which shipments are included. The example data is deliberately small enough to check without relying on a chart.

English formulas here use commas between arguments. Follow the separator shown by your configured editor. The current help reference does not prove first-version availability or identical behaviour across every ONLYOFFICE desktop, browser and mobile build.

For the same statistical question in other programs, see RANK.EQ in Microsoft Excel, RANK.EQ in Google Sheets, RANK.EQ in SoftMaker PlanMaker. These links identify corresponding measures, not a guarantee that names, mixed-data rules, error codes or file conversions are identical.

MEDIAN, LARGE, SMALL, STDEV.S, STDEV.P, VAR.S, VAR.P. Browse the ONLYOFFICE function library for the other published guides.

Editorial verification: The vendor documentation was reviewed on 2026-10-12. Scope: The ONLYOFFICE spreadsheet function reference. The reviewed help does not establish the first supported version or identical desktop, browser and mobile behaviour. Three numeric examples were checked with an independent arithmetic model. No native application run was performed. Single-value population edge cases, mixed-data coercion, exact error-code parity and round-trip workbook compatibility remain untested; they are not labelled application-verified.