FIB Function (Gnumeric)
Use FIB in Gnumeric for Fibonacci numbers, with worked recurrence checks, input rules and native evidence of large-index precision limitations.
Verification status: 19 reference, boundary and advanced-check formulas were recalculated with Gnumeric 1.12.57 ssconvert. Retained native records and independent calculations were checked. Version 1.12.62 was source-checked only. Large-index numerical discrepancies are explicitly retained. How formula examples are checked
Precision warning: The tested build does not reliably return exact Fibonacci integers for indices above 46. =FIB(78) returned 8944394323791488, while the exact integer is 8944394323791464. The 1.12.62 source still switches to a floating-point formula at this point.
Quick answer: =FIB(2) gives 1 in the tested Gnumeric 1.12.57 build.
Availability and version history
- Introduced: Gnumeric 1.1.9 release notes explicitly record this function being added.
- Supported in: Gnumeric 1.12.62; no retirement is established.
- Scope: Desktop Gnumeric with the Mathematics plugin. English comma-separated formulas are shown.
- Checked: October 14, 2026. Tables and the named advanced check were recalculated through 1.12.57 ssconvert. Current 1.12.62 source was inspected; the later release was not executed.
What FIB returns
FIB returns the Fibonacci sequence indexed with F₁ = F₂ = 1 and Fₙ = Fₙ₋₁ + Fₙ₋₂. Use it to explore recurrences or modest sequence indices. It is not an arbitrary-precision integer calculator. Versioned function help.
Syntax and arguments
=FIB(n)
| Argument | Meaning |
|---|---|
n |
Positive index. Positive fractions are rounded down before evaluation. Zero and negative inputs fail. |
Reproducible examples
Ordinary results are rounded to twelve decimal places; tiny values use scientific notation. FIB results retain the native captured digits so approximation is visible. The eight reference rows were independently checked.
| Formula | Gnumeric 1.12.57 result |
|---|---|
=FIB(1) |
1 |
=FIB(2) |
1 |
=FIB(3) |
2 |
=FIB(10) |
55 |
=FIB(20) |
6765 |
=FIB(23) |
28657 |
=FIB(30) |
832040 |
=FIB(46) |
1836311903 |
Practical worksheet
Enter indices 1 through 10 in A2:A11. In B2 enter =FIB(A2) and fill down. The sequence should be 1, 1, 2, 3, 5, 8, 13, 21, 34, 55. To compare the recurrence, enter =B3+B2 in C4 and fill down beside B4:B11. This layout is a reproducible worksheet exercise; the direct calls in the tables were the executed checks.
The indexing matters: some mathematical definitions include F₀ = 0, but Gnumeric rejects index zero. Shift your source indices deliberately rather than replacing every error with zero.
Advanced interpretation and checks
The executed check =FIB(20)-FIB(19)-FIB(18) returned 0, agreeing with 6765 − 4181 − 2584. This verifies the recurrence for that modest index.
The current implementation keeps integer values through index 46, then uses Binet’s expression involving powers of (1 + √5)/2 and (1 − √5)/2. At index 47 the native result was 2971215073.000005 instead of exact 2971215073. At 78 the error was 24. Rounding to an integer would hide the first discrepancy but would not fix the second. Exact large-integer work needs an independently verified integer method and a number representation capable of holding the answer.
Boundaries and troubleshooting
Validate the index before generating a sequence. The tested 5.9 input became index 5, while 0.9 became zero and failed. A blank reference is treated as zero here. TRUE became 1. The high-index limitations above are actual 1.12.57 observations; the retained later-source branch supports the warning but does not establish identical later-build output.
F5 is an actually empty cell. Listed errors are native error results, not mathematical zeroes.
| Formula | Gnumeric 1.12.57 result |
|---|---|
=FIB(0) |
#NUM! |
=FIB(-1) |
#NUM! |
=FIB(0.9) |
#NUM! |
=FIB(5.9) |
5 |
=FIB(47) |
2971215073.000005 |
=FIB(78) |
8944394323791488 |
=FIB("abc") |
#VALUE! |
=FIB(F5) |
#NUM! |
=FIB(TRUE()) |
1 |
=FIB() |
#N/A |
Official evidence and checking scope
The retained workbook contained a deliberately stale SUM cache and an uncached SUM formula, both recalculated correctly. Native evidence covers the listed 1.12.57 cases; worksheet layouts and algebraic interpretations are independently specified explanations. Other locales, direct GUI entry and later-release output were not tested.