Contact

RANK.EQ in Collabora Office: Shared Tied Ranks, Gaps and Top-Rank Thresholds

Statistical Intermediate Collabora Office Calc

Use Collabora RANK.EQ for competition-style tied ranks, understand skipped positions and avoid treating a rank cutoff as a fixed row quota.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: RANK.EQ gives duplicate numeric values the same lower numerical rank among their occupied positions. The next distinct value can therefore skip ranks. Descending order is the default; type 1 requests ascending order.

Availability and version history

  • Introduced: original Collabora release and launch date are not established by the reviewed sources.
  • Availability: currently documented in Collabora Office 26.04 desktop help.
  • Platform scope: online and mobile deployments are not inferred from this desktop-help release.
  • Checked: October 14, 2026. Function-specific documentation and independent calculations; no native Collabora execution.

Syntax and order choice

=RANK.EQ(value;data;[type])

The data argument is a range or array. Type 0, also used when omitted, is descending; type 1 is ascending. The dedicated source does not certify every other nonzero type argument, so the examples use only those documented choices.

The ranking convention is often called competition ranking. It differs from dense ranking, where successive distinct values receive consecutive ranks without gaps.

Example 1: tied observations and skipped positions

Enter 90,70,90,50,70 in A2:A6. In B2 enter and fill downward:

=RANK.EQ(A2;$A$2:$A$6)

Expected results:

Value Descending rank
90 1
70 3
90 1
50 5
70 3

The 90s occupy positions 1 and 2, and both receive 1. The 70s occupy positions 3 and 4, and both receive 3. The 50 receives 5. The gaps reflect tied observations that still occupy places in the ordered list.

The comparison range is absolute so it does not drift when the formula is filled. Source rows remain in their original order.

Example 2: ascending ties use the same lower-rank rule

For ascending order:

=RANK.EQ(A2;$A$2:$A$6;1)

The expected row-by-row results are 4,2,4,1,2. The 50 has rank 1, the two 70s share rank 2, and the two 90s share rank 4.

Unlike averaged ranks, the descending and ascending RANK.EQ values here do not all sum to six. For a tied 90 they sum to five, while the unique 50’s pair sums to six. Do not apply an average-rank identity to this different tie convention.

Advanced example: a top-three rank is not three rows

Using the descending ranks, select every row satisfying:

=B2<=3

Filled through B6, the expected conditions are TRUE,TRUE,TRUE,FALSE,TRUE. Four rows qualify because the cutoff includes both values tied at rank 3.

A report requiring exactly three rows needs an additional explicit tie-breaking rule, such as a second unique identifier or another approved criterion. RANK.EQ alone does not supply that rule, and silently removing one tied row would change the selection policy.

Advanced comparison: dense and averaged ranks

For the original values, dense descending ranks would be 1,2,1,3,2. Those are a separate mathematical comparison, not RANK.EQ output.

RANK.AVG instead yields 1.5,3.5,1.5,5,3.5, averaging each tie group’s occupied positions. Its ranks total 15, whereas the RANK.EQ ranks total 13. Neither sum is a reason to round or adjust the actual RANK.EQ results.

For four identical observations 8,8,8,8, every RANK.EQ is 1 in either direction. RANK.AVG would give 2.5 to each.

Advanced check: changing the cohort

Add 100 and expand the comparison range. Original descending ranks become 2,4,2,6,4, and the new observation has rank 1. Original values are unchanged; their relative positions change because the comparison set changed.

Errors, type scope and compatibility

An absent requested value produces an error according to the source, but its exact display is not established here. Text, Boolean, formula-empty and source-error conversions remain unverified for this dedicated section.

The help names COM.MICROSOFT.RANK.EQ outside the cited OpenFormula 1.3 standard. This is a format-identity detail, not a native export/import guarantee or retirement notice. RANK has its own current documentation and should not be assumed to share every boundary rule.

References and verification

Complete function-specific documentation reviewed. Worked outputs are independent mathematical or explicitly documented rule controls, not application screenshots or native test results. Unresolved ordering, type and error boundaries retain their stated scope.