RANK in Collabora Office: Ascending and Descending Positions with Unique Values
Use Collabora RANK with its default descending order, explicit ascending controls and fixed comparison ranges without assuming tie behavior.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
Quick answer: RANK returns a number’s position within a supplied dataset. Collabora defaults to descending order with type 0; type 1 requests ascending order. The number must occur within the data, or the source says an error is displayed.
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 default
=RANK(value;data;[type])
- value is the numeric observation whose rank you need.
- data is the comparison array or range.
- type is optional: 0 is descending and 1 is ascending.
The dedicated reference explicitly ignores text and empty cells within a data range. It does not fully define duplicate handling, other type values or exact missing-value error codes. The principal examples therefore use unique numeric observations.
Example 1: descending ranks with a fixed cohort
Enter 45,20,80,60 in A2:A5. Put this in B2 and fill through B5:
=RANK(A2;$A$2:$A$5)
Expected results in the original row order are:
| Value | Descending rank |
|---|---|
| 45 | 3 |
| 20 | 4 |
| 80 | 1 |
| 60 | 2 |
The highest value is rank 1. The absolute comparison reference stays A2:A5 when you fill downward; only the value reference changes.
The formula calculates a rank without sorting or rearranging the source rows. If a report needs sorted rows as well, that is a separate operation.
Example 2: ascending order is an explicit choice
In C2, fill this formula through C5:
=RANK(A2;$A$2:$A$5;1)
Expected ranks are 2,1,4,3. The smallest observation, 20, now has rank 1. For this unique four-value dataset, each descending rank plus its ascending rank equals 5.
Type 0 explicitly reproduces the first example’s default. These controls do not establish what every other nonzero or non-integer type argument does.
Advanced example: change the comparison cohort
Add 100 in A6. Ranking the original values against A2:A6 gives descending ranks 4,5,2,3, and the new 100 has rank 1. Every old descending rank increases by one.
Their ascending ranks remain 2,1,4,3, while 100 takes ascending rank 5. A rank describes relative position in a particular comparison set; it is not an intrinsic property that remains fixed when the cohort changes.
In a copied report, label both the observation and the period, region or other rule defining its comparison range.
Advanced checks: reorder and rescale
Reorder the original values as 80,60,45,20. The descending ranks in that new row order are 1,2,3,4, but each original value retains its rank within the same four-value cohort.
Adding 100 to every value gives 145,120,180,160 and preserves the original descending ranks 3,4,1,2. Multiplying every value by -1 gives -45,-20,-80,-60, reversing the numeric ordering; descending ranks become 2,1,4,3.
These checks distinguish row order from numerical order and show why a negative scale is not the same as adding a constant.
Text, missing values and duplicate policy
Adding text Pending and a genuinely empty cell to the original comparison range does not add ranked numeric observations under the documented range-ignore rule. Asking for 50, which is absent, reaches the documented error condition; the exact error display remains unverified here.
The compact RANK section does not explicitly establish a tie rule. RANK.AVG and RANK.EQ have direct duplicate-handling documentation and are better-described choices when tied values are expected.
RANK remains currently documented. A similar purpose or newer-looking spelling does not prove retirement, a complete alias, or identical mixed-type behavior across all three functions.
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.