LARGE in ONLYOFFICE: Nth-Largest Values and Ties

Use LARGE in ONLYOFFICE to return the value at a chosen position when the observations are ordered from largest to smallest. The working example below describes delivery lead times; its result is measured in 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.

LARGE(array, k)

Data range: a numeric range such as A2:A9. Each included observation occupies a position, even when two values are equal.

Position: a positive integer such as 2 for the second observation. The example uses no fractional positions and requires enough numeric data for the requested position.

Use LARGE for the second-highest, third-highest or another high-end observation without rearranging the source records. A single requested position produces a number, not a sorted copy of the register and not the name or identifier attached to that number.

Repeated observations occupy repeated positions. This is useful when you want the top three transactions, including tied amounts. It is the wrong calculation when the requirement is the top three different amounts. Decide which interpretation the report needs before removing duplicates: a real repeated transaction is not necessarily a data-entry mistake.

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 LARGE 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: Find the second-highest observation

=LARGE(A2:A9,2)

Expected result: 26.

In the requested direction the observations are 30, 26, 22, 22, 18, 18, 14, 10. Position 2 supplies 26. The result is the measurement, not the original row number.

Example 2: Use a position cell and a fixed comparison range

Set D2 to 3 before entering the formula.

=LARGE($A$2:$A$9,D2)

Expected result: 22.

Enter 3 in D2. The formula requests position 3 while keeping the register fixed. For a list of positions, enter consecutive integers below D2 and copy the formula down; keep each position within the numeric count of 8.

Example 3: Check duplicates, zero and negative values

For this check, use F2:F6 containing -8, -3, 0, 6, 6, in that order. These values are included in the practice file.

=LARGE(F2:F6,2)

Expected result: 6.

The two equal values of 6 occupy the first two descending positions. LARGE returns observations, not unique amounts, so position 2 is also 6.

The numeric model sorts a copy of the observations and selects the requested one-based position. It retains duplicates and signed values. The production formula examples use ordinary single-result calls; no claim is made about passing an array of positions or automatic spill behaviour. 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.

The same result appears more than once. Tied observations occupy separate positions. Do not promise a list of distinct values from successive LARGE calls.

The requested position is invalid. Use a whole-number position from 1 through the number of numeric observations. This guide does not rely on an application’s treatment of fractional positions. An empty input or a position beyond the numeric count needs a visible validation message, not an invented zero.

Copied formulas inspect different records. Lock the data range with dollar signs while allowing the requested-position cell to change. Also keep the input register separate from result cells so a summary value is not included in its own calculation.

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 LARGE in Microsoft Excel, LARGE in Google Sheets, LARGE in SoftMaker PlanMaker. These links identify corresponding measures, not a guarantee that names, mixed-data rules, error codes or file conversions are identical.

MEDIAN, SMALL, RANK.EQ, 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.