Zoho Sheet OCT2DEC Function: Octal to Decimal with Examples

OCT2DEC(octal_number)

Zoho’s official OCT2DEC entry was checked on October 15, 2026. It describes the rolling web service. The first supported release and last functioning version are unknown; current documentation is separate from those historical endpoints. Mobile/offline parity is unverified. Results below are independent integer calculations, not native Zoho execution.

The required source contains at most ten characters, using only 0 through 7. Numeric literals in the examples are digit sequences in the source base, not ordinary decimal quantities. The checked entry does not fully specify signed interpretation of maximum-width values; these examples use small positive values and make no unsigned or two’s-complement promise at that boundary.

There is no output-width argument. Leading zeroes used only for a source identifier’s layout are not preserved by conversion to a decimal quantity. Keep the original input when its exact written form matters.

Zoho explicitly gives =OCT2DEC(77) with result 63. This provides a compact starting control before working with cell references. Other vendor examples refer to cells whose inputs are not visible in the extracted help; the complete worksheet below supplies its own inputs rather than inventing those hidden cells.

Create Conversions with Source in A1, Decimal_check in B1, Converted in C1. Enter the following values in A2:B7. Enter the source numerals exactly as shown, without grouping commas or base prefixes. Column B is an independent explanatory value, not an argument to the conversion formula.

Enter C2 =OCT2DEC(A2) and fill through C7.

In a copy change A5 from 52 to 53 and update its explanatory B5 to 43. C5 becomes 43. Other records remain unchanged. This gives a one-unit sensitivity check with a fully specified input.

Suppose an instrument’s documentation explicitly labels its counter readings as octal. Put 17 and 20 in G2:G3 and fill H2 =OCT2DEC(G2) through H3. The expected decimal readings are 15 and 16. I3 =H3-H2 is 1; subtracting the original visible numerals would instead give 3, which is not the counter increment.

For a three-digit control, =OCT2DEC(751) gives 489, independently checked as 7×64+5×8+1. If the next reading is 752, its decimal value is 490 and the increment is again one. This example assumes ordinary positive values with no counter wraparound. A real device may define a modulus or signed encoding that needs its own documented handling.

Keep the raw input column unchanged, add the converted decimal column, and perform differences or summaries on that numeric column. Do not apply OCT2DEC merely because a column happens to contain digits 0–7; ordinary decimal values often do too. The source format, rather than the character pattern alone, establishes the intended base.

The official entry identifies invalid source digits as #NUM!. Thus OCT2DEC(8) is an invalid-digit control. Respect the ten-character input contract; the checked page does not separately establish an exact error token for every overlength, signed or malformed value.

The shared help glossary mentions name, type and reference errors without defining a complete coercion matrix for this function. Check the source base, legal characters, cell type and literal quotation before investigating more complex formulas. Do not add 0x, 0b or other programming-language prefixes unless a product reference explicitly permits them.

Keep conversion and arithmetic separate. A nondecimal display can look like a decimal number, yet ordinary subtraction on that display need not measure the intended change. Preserve raw identifiers, document the source’s sign and width convention, and verify exported leading zeroes in the receiving system. Matching function names across spreadsheet products do not establish identical limits or behavior.