RANK.EQ in Zoho Sheet: Ranking Direction and Equal Values

Use RANK.EQ in Zoho Sheet to assign an observation its position in a numeric list, giving tied values the same best position. The working example below describes ticket handling times; it returns a position, not minutes. 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 Zoho Sheet.

RANK.EQ(number; number_list; [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 browser-based service register with one row per handled ticket provides the scenario. Enter the following numeric observations into A2:A10, one per row, with a header in A1. Use a spare result cell outside the input range.

Download the Zoho Sheet 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$10;0)

Expected result: 8.

A2 contains 6. There are 7 observations greater than 6, 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(10;A2:A10;0)

Expected result: 6.

The value 10 occurs 2 times. Each occurrence receives rank 6; 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$10;1)

Expected result: 2.

The nonzero/true direction switches to ascending order. There are 1 observations below 6, 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 Zoho reference documents the RANK.EQ name and its worksheet inputs.

The worked inputs contain only explicit numeric observations. A generic error-description block in the help is not treated as proof that every listed error applies to this particular formula. See the function-specific Zoho help.

The formulas follow Zoho’s documented semicolon-separated form. Do not replace the colon inside a range such as A2:A10: it still means all the cells between those endpoints. If your configured editor expects a different argument separator, use the one it displays.

In the service-register example, keep ticket handling time separate from time waiting for a customer. Record one intended observation per row before summarising the list. The function cannot tell which part of a ticket lifecycle a number represents. Native Zoho runs, mixed-type coercion tests and desktop/mobile comparisons are outside this guide’s verification scope.

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

MEDIAN, LARGE, SMALL, STDEV, STDEVP, VAR, VARP. Browse the Zoho Sheet function library for the other published guides.

Editorial verification: The vendor documentation was reviewed on 2026-10-12. Scope: Zoho Sheet public web help and its documented English formula names. Desktop/mobile parity and first-release dates have not been established here. 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.