BIN2OCT in Collabora Office: Group Binary Digits into Explicit Octal Fields

• 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.

=BIN2OCT(Number [; Places])

Number is a binary string of at most ten bits. Its negative representation uses the documented sign bit and two’s-complement convention. Places is the number of output positions and is optional.

The reference does not specify the omitted Places default, all output-width limits or fractional-argument treatment. These examples supply integer Places and use positive binary inputs no larger than 511. Negative-output formatting and exact native error codes remain unverified.

Octal uses only digits 0 through 7. One octal digit represents three binary positions, because 2^3=8. Digit 8 is not a valid octal digit even though it is an ordinary decimal digit.

Enter these exact strings in Text-formatted A2:A7. In B2 use =BIN2OCT(A2;3) and fill down.

The decimal values are explanatory controls. Use =BIN2DEC(A2) in C2 and fill down to calculate them separately.

The change from binary 111 to 1000 crosses from decimal 7 to 8. In octal the corresponding change is 7 to 10, shown here as 007 to 010. It is not a jump from decimal seven to decimal ten.

For input 101011110, group from the right as 101 011 110. These groups have values 5, 3 and 6, giving octal 536.

=BIN2OCT("101011110";3)
=BIN2DEC("101011110")

Independently expected results are text 536 and number 350. The positional check is 5×64+3×8+6=350.

For an input whose length is not a multiple of three, leading zeros complete the leftmost group. Binary 101010 groups as 101 010 and yields 52; explicit Places 3 adds a leading output zero to give 052.

A record specification defines six binary characters as two unsigned three-bit fields. Enter 101011 in E2.

=BIN2OCT(LEFT(E2;3);1)
=BIN2OCT(RIGHT(E2;3);1)
=BIN2OCT(E2;2)

The outputs are 5, 3 and 53, all text representations. The complete decimal quantity is 5×8+3=43, rather than the sum 5+3=8.

Use =BIN2DEC(E2) for the separate expected numeric result 43. LEFT and RIGHT respect this particular field definition. A different specification may require different boundaries.

=BIN2OCT("1100100";4) returns 0144, which is the official source’s documented example. Compare it with explicit width 3, whose independent expected result is 144. Both represent 100.

If B2:B7 contains the first table’s output, use =OCT2DEC(B2) in D2 and fill down. Expected values are again 1, 7, 8, 42, 100 and 511. Numeric equality does not prove that the original field width was preserved: 052 and 52 decode to the same value.

Keep octal codes as text when their leading zeros matter. Adding their displayed digits as if they were decimal quantities answers a different question. Decode first when arithmetic is intended, using OCT2DEC.

The function’s ten-bit input contract differs from the ten-octal-character contract of OCT2DEC. Ten binary digits and ten octal digits do not have the same capacity. Full-width negative binary inputs must also not be treated as ordinary unsigned values.

This guide does not certify invalid-digit errors, negative output padding, omitted Places or overflow behavior. It supplies explicit positive fixtures that can be independently checked without borrowing those missing rules from Excel or another Calc distribution.

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

Complete function-specific documentation reviewed. Outputs are independently calculated positional models or explicitly documented controls, not captured native application results. Formulas use English names and semicolon separators; optional-argument brackets describe syntax and are not typed into a working formula.