AREAS in Collabora Office: Count Separate Reference Areas, Not Their Cells

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

=AREAS(Reference)

AREAS expects one argument. To combine multiple ranges, the Collabora help requires an extra pair of parentheses around the combined reference. Its examples accept semicolon-separated ranges inside those parentheses and automatically convert that separator to the tilde (~) union operator.

Use the explicit documented union form for the worked examples:

=AREAS((A2:B4~F2~H2:H5))

The expected result is 3. This combines a two-column rectangle, a single cell and a one-column rectangle into one multiple-range argument.

The parentheses are important. Writing several ordinary function arguments is not the same as passing one grouped reference. Do not import another spreadsheet’s union punctuation without checking Collabora’s syntax.

Inspect the three components of the primary reference:

The components contain 11 cells altogether, but AREAS returns 3. Each contiguous component contributes one to the area count regardless of its size.

The ranges are deliberately disjoint, so the cell total is simply 6+1+4. That arithmetic does not certify how repeated or overlapping references are normalized by the native application.

Evaluate these separately in free cells outside the referenced ranges:

=AREAS(A2:B4)
=AREAS(A2:D8)
=AREAS(F2)

All three have expected result 1. The second rectangle has 7 rows and 4 columns, or 28 cells, but is still a single continuous area.

If the task is to count rows or columns of a rectangle, use ROWS or COLUMNS instead. Multiplying those two dimension counts gives the rectangle’s cell count, not its number of populated cells.

Suppose a report keeps three monthly sections in A2:B4, D2:E4 and G2:H4:

=AREAS((A2:B4~D2:E4~G2:H4))

Expected result: 3. Each section has six cells, so these disjoint sections contain 18 cells in total.

A single bounding rectangle A2:H4 contains 24 cells, including the separator columns C and F, but =AREAS(A2:H4) returns 1. A bounding rectangle and a union of selected blocks are different references, even when they cover the same outermost columns and rows.

This distinction helps audit a formula specification: “all cells between the endpoints” does not necessarily mean “only the three intended sections.” AREAS reveals the reference structure but does not verify that the chosen blocks contain the right records.

Enter numbers in A2:B4, then change one to text and clear another. =AREAS(A2:B4) still describes one reference area under the documented definition. Its purpose is independent of whether the cells are blank, numeric or textual.

Likewise, a formula returning empty text does not create a new area or split a rectangle. Use an appropriate counting function for the data-quality question instead of treating AREAS as a completeness test.

For a named-area control, define BlockOne as A2:B4 in the workbook’s range-definition interface. =AREAS(BlockOne) has expected result 1, following the official single named-area example. The name identifies the reference; it does not add another layer to the area count.

The short reference does not pin exact native behavior for overlapping unions, repeated components, 3-D sheet ranges or invalid text arguments. Those cases remain outside these disjoint-area controls.

AREAS returns a structural count, not the referenced values. Retain a visible list of the component ranges when auditing a larger union. A result of 3 confirms only the modeled number of areas; it cannot establish that all three have the same dimensions or that each contains the intended monthly data.

• Collabora Office 26.04: AREAS.
• Editorial testing standards.

Complete function-specific documentation reviewed. Worked outputs are independently modeled reference, text or arithmetic controls, not captured native application results. Unverified entry, conversion and error boundaries retain their stated scope.