PERMUT
Quirk foundCategory: Statistical · Last tested 2026-09-01
Real compatibility results for the PERMUT function: executed in Excel for the web, Google Sheets and LibreOffice Calc, with desktop Excel behavior from Microsoft’s official documentation (we do not run desktop Excel — Excel for the web is a different application and is executed separately). Syntax and links to that documentation are below.
Support matrix
| Engine | Documented | Live-tested | Verdict |
|---|---|---|---|
| Excel (desktop) | Yes | No — documented only | n/a |
| Excel for the web | — | Yes (recalc, 2026-09-01) | Quirk found |
| Google Sheets | Yes | Yes (Drive import, 2026-08-31) | Quirk found |
| LibreOffice Calc | Yes | Yes (25.8.7.3, 2026-08-31) | Quirk found |
LibreOffice version history
We executed the same test cases under each LibreOffice release to show exactly when PERMUT’s support changed — not documentation claims, real results.
| LibreOffice version | Verdict | Tested |
|---|---|---|
| 24.2.0.3 | Quirk found | 2026-08-31 |
| 24.8.7.2 | Quirk found | 2026-08-31 |
| 25.2.0.3 | Quirk found | 2026-08-31 |
| 25.8.7.3 | Quirk found | 2026-08-31 |
Why isn't PERMUT working in LibreOffice?
PERMUT exists in LibreOffice 25.8.7.3, but it is not a drop-in match for
Excel — our executed tests found real behavioral differences (detailed in the test results on this
page). If a formula that works in Excel or Google Sheets misbehaves in LibreOffice, compare your usage
against the failing cases above before assuming your data is wrong.
Why isn’t PERMUT working in Google Sheets?
PERMUT runs in Google Sheets, but our executed cases show it does not match
Excel’s documented behavior on every input (the failing cases are listed on this page). If a
formula that behaves one way in Excel gives you a different answer in Sheets, compare your usage
against those cases before assuming your data is wrong.
Discovered quirks
-
=PERMUT(0,0) on
Excel for the web returned
1, but the documented/expected
result is #NUM!.
Provenance
Microsoft documents: "If number <= 0 or if number_chosen < 0, PERMUT returns the #NUM! error value." Zero is the boundary the <= includes, so PERMUT(0,0) is an error even though the empty arrangement of an empty set is mathematically 1 -- and note that PERMUTATIONA, the sibling function, documents the opposite treatment of the same input. That disagreement between two Microsoft pages is itself worth pinning. EXECUTED RESULT -- A SILENT WRONG ANSWER: LibreOffice returns 1 on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3), which agree case for case, where Excel documents #NUM!. Mathematically 1 is defensible -- there is exactly one arrangement of nothing -- but it is not what Microsoft's page specifies, and the disagreement is invisible: no error, no warning, just a number where Excel gives an error. Note that LibreOffice is here MORE permissive than Excel, the opposite direction from most of this batch's divergences.; MISMATCH vs expected: expected '#NUM!', got 1
-
=PERMUT(0,0) on
Google Sheets returned
1, but the documented/expected
result is #NUM!.
Provenance
Microsoft documents: "If number <= 0 or if number_chosen < 0, PERMUT returns the #NUM! error value." Zero is the boundary the <= includes, so PERMUT(0,0) is an error even though the empty arrangement of an empty set is mathematically 1 -- and note that PERMUTATIONA, the sibling function, documents the opposite treatment of the same input. That disagreement between two Microsoft pages is itself worth pinning. EXECUTED RESULT -- A SILENT WRONG ANSWER: LibreOffice returns 1 on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3), which agree case for case, where Excel documents #NUM!. Mathematically 1 is defensible -- there is exactly one arrangement of nothing -- but it is not what Microsoft's page specifies, and the disagreement is invisible: no error, no warning, just a number where Excel gives an error. Note that LibreOffice is here MORE permissive than Excel, the opposite direction from most of this batch's divergences.; MISMATCH vs expected: expected '#NUM!', got 1
-
=PERMUT(2,3) on
LibreOffice Calc returned
#VALUE!, but the documented/expected
result is #NUM!.
Provenance
Microsoft documents: "If number < number_chosen, PERMUT returns the #NUM! error value."; MISMATCH vs expected: expected '#NUM!', got '#VALUE!'
-
=PERMUT(0,0) on
LibreOffice Calc returned
1, but the documented/expected
result is #NUM!.
Provenance
Microsoft documents: "If number <= 0 or if number_chosen < 0, PERMUT returns the #NUM! error value." Zero is the boundary the <= includes, so PERMUT(0,0) is an error even though the empty arrangement of an empty set is mathematically 1 -- and note that PERMUTATIONA, the sibling function, documents the opposite treatment of the same input. That disagreement between two Microsoft pages is itself worth pinning. EXECUTED RESULT -- A SILENT WRONG ANSWER: LibreOffice returns 1 on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3), which agree case for case, where Excel documents #NUM!. Mathematically 1 is defensible -- there is exactly one arrangement of nothing -- but it is not what Microsoft's page specifies, and the disagreement is invisible: no error, no warning, just a number where Excel gives an error. Note that LibreOffice is here MORE permissive than Excel, the opposite direction from most of this batch's divergences.; MISMATCH vs expected: expected '#NUM!', got 1
Executed test cases
Excel for the web (executed 2026-09-01 via OneDrive recalculation)
These values come from Excel for the web, not from desktop Excel. They are two different implementations of the calculation engine, and this run measured only the web one: the corpus was uploaded to OneDrive as .xlsx, recalculated by Excel for the web on open, and downloaded again for readback. Excel for the web is a rolling service with no pinnable version, so the run is identified by its date. Where a value here disagrees with the Expected column — which is Microsoft’s documentation of the desktop product — we cannot tell you whether the web engine diverges from the desktop one or the documentation is wrong about both, because we do not run desktop Excel.
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =PERMUT(A2,A3) | Microsoft's documented worked example | 970200 | 970200ProvenanceMicrosoft publishes =PERMUT(A2,A3) = 970200 for 100 objects taken 3 at a time. DERIVATION in exact integer arithmetic from the documented equation n!/(n-k)!: 100 x 99 x 98 = 970200 exactly. No factorial of 100 is ever formed -- the ratio telescopes to the product of the top k terms, which is both the honest reading of the formula and the only way to evaluate it without overflow. Microsoft's page was re-read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/permut-function (the /en-us/office/<name>-function-<guid> path was serving Microsoft's 'Sorry, the page you're looking for can't be found' body throughout this batch, and the working path returns an 87 KB stub about half the time, so pages were fetched with retries until the payload exceeded 150 KB). |
Matched |
| =PERMUT(3,2) | Microsoft's second documented row | 6 | 6ProvenanceMicrosoft publishes =PERMUT(3,2) = 6, "Permutations possible for a group of 3 objects where 2 are chosen". 3!/1! = 3 x 2 = 6, and the six orderings can be written out by hand, so this case is verifiable without arithmetic at all. |
Matched |
| =PERMUT(5,0) | Choosing zero objects, which the documented equation forces to 1 | 1 | 1Provenancen!/(n-0)! = 1 for every n: there is exactly one arrangement of nothing. Microsoft does not print this row, but the value is forced by the equation the page does print, and the page's error list explicitly permits number_chosen = 0 (it errors only "If number <= 0 or if number_chosen < 0"). The empty permutation is the classic off-by-one in a hand-rolled implementation. |
Matched |
| =PERMUT(3.9,2.9) | Fractional arguments, which the page says are truncated | 6 | 6ProvenanceMicrosoft documents: "Both arguments are truncated to integers." Truncation (not rounding) of 3.9 and 2.9 gives 3 and 2, so this must return PERMUT(3,2) = 6. An engine that ROUNDED instead would compute PERMUT(4,3) = 24 -- a four-fold difference, which makes this a decisive one-value test of the documented rule. |
Matched |
| =PERMUT(2,3) | Choosing more objects than exist, which the page excludes | #NUM! | #NUM!ProvenanceMicrosoft documents: "If number < number_chosen, PERMUT returns the #NUM! error value." |
Matched |
| =PERMUT(0,0) | Zero objects, which the page excludes even when nothing is chosen | 1 | #NUM!ProvenanceMicrosoft documents: "If number <= 0 or if number_chosen < 0, PERMUT returns the #NUM! error value." Zero is the boundary the <= includes, so PERMUT(0,0) is an error even though the empty arrangement of an empty set is mathematically 1 -- and note that PERMUTATIONA, the sibling function, documents the opposite treatment of the same input. That disagreement between two Microsoft pages is itself worth pinning. EXECUTED RESULT -- A SILENT WRONG ANSWER: LibreOffice returns 1 on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3), which agree case for case, where Excel documents #NUM!. Mathematically 1 is defensible -- there is exactly one arrangement of nothing -- but it is not what Microsoft's page specifies, and the disagreement is invisible: no error, no warning, just a number where Excel gives an error. Note that LibreOffice is here MORE permissive than Excel, the opposite direction from most of this batch's divergences. |
Mismatch |
| =PERMUT("x",2) | A non-numeric argument | #VALUE! | #VALUE!ProvenanceMicrosoft documents: "If number or number_chosen is nonnumeric, PERMUT returns the #VALUE! error value." |
Matched |
Google Sheets (executed 2026-08-31 via Drive import)
Google Sheets is a rolling service with no pinnable version, so this run is identified by its date. The corpus was imported to Drive as .xlsx, recalculated by Sheets, and exported back for readback.
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =PERMUT(A2,A3) | Microsoft's documented worked example | 970200 | 970200ProvenanceMicrosoft publishes =PERMUT(A2,A3) = 970200 for 100 objects taken 3 at a time. DERIVATION in exact integer arithmetic from the documented equation n!/(n-k)!: 100 x 99 x 98 = 970200 exactly. No factorial of 100 is ever formed -- the ratio telescopes to the product of the top k terms, which is both the honest reading of the formula and the only way to evaluate it without overflow. Microsoft's page was re-read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/permut-function (the /en-us/office/<name>-function-<guid> path was serving Microsoft's 'Sorry, the page you're looking for can't be found' body throughout this batch, and the working path returns an 87 KB stub about half the time, so pages were fetched with retries until the payload exceeded 150 KB). |
Matched |
| =PERMUT(3,2) | Microsoft's second documented row | 6 | 6ProvenanceMicrosoft publishes =PERMUT(3,2) = 6, "Permutations possible for a group of 3 objects where 2 are chosen". 3!/1! = 3 x 2 = 6, and the six orderings can be written out by hand, so this case is verifiable without arithmetic at all. |
Matched |
| =PERMUT(5,0) | Choosing zero objects, which the documented equation forces to 1 | 1 | 1Provenancen!/(n-0)! = 1 for every n: there is exactly one arrangement of nothing. Microsoft does not print this row, but the value is forced by the equation the page does print, and the page's error list explicitly permits number_chosen = 0 (it errors only "If number <= 0 or if number_chosen < 0"). The empty permutation is the classic off-by-one in a hand-rolled implementation. |
Matched |
| =PERMUT(3.9,2.9) | Fractional arguments, which the page says are truncated | 6 | 6ProvenanceMicrosoft documents: "Both arguments are truncated to integers." Truncation (not rounding) of 3.9 and 2.9 gives 3 and 2, so this must return PERMUT(3,2) = 6. An engine that ROUNDED instead would compute PERMUT(4,3) = 24 -- a four-fold difference, which makes this a decisive one-value test of the documented rule. |
Matched |
| =PERMUT(2,3) | Choosing more objects than exist, which the page excludes | #NUM! | #NUM!ProvenanceMicrosoft documents: "If number < number_chosen, PERMUT returns the #NUM! error value." |
Matched |
| =PERMUT(0,0) | Zero objects, which the page excludes even when nothing is chosen | 1 | #NUM!ProvenanceMicrosoft documents: "If number <= 0 or if number_chosen < 0, PERMUT returns the #NUM! error value." Zero is the boundary the <= includes, so PERMUT(0,0) is an error even though the empty arrangement of an empty set is mathematically 1 -- and note that PERMUTATIONA, the sibling function, documents the opposite treatment of the same input. That disagreement between two Microsoft pages is itself worth pinning. EXECUTED RESULT -- A SILENT WRONG ANSWER: LibreOffice returns 1 on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3), which agree case for case, where Excel documents #NUM!. Mathematically 1 is defensible -- there is exactly one arrangement of nothing -- but it is not what Microsoft's page specifies, and the disagreement is invisible: no error, no warning, just a number where Excel gives an error. Note that LibreOffice is here MORE permissive than Excel, the opposite direction from most of this batch's divergences. |
Mismatch |
| =PERMUT("x",2) | A non-numeric argument | #VALUE! | #VALUE!ProvenanceMicrosoft documents: "If number or number_chosen is nonnumeric, PERMUT returns the #VALUE! error value." |
Matched |
LibreOffice Calc 25.8.7.3 (tested 2026-08-31)
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =PERMUT(A2,A3) | Microsoft's documented worked example | 970200 | 970200ProvenanceMicrosoft publishes =PERMUT(A2,A3) = 970200 for 100 objects taken 3 at a time. DERIVATION in exact integer arithmetic from the documented equation n!/(n-k)!: 100 x 99 x 98 = 970200 exactly. No factorial of 100 is ever formed -- the ratio telescopes to the product of the top k terms, which is both the honest reading of the formula and the only way to evaluate it without overflow. Microsoft's page was re-read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/permut-function (the /en-us/office/<name>-function-<guid> path was serving Microsoft's 'Sorry, the page you're looking for can't be found' body throughout this batch, and the working path returns an 87 KB stub about half the time, so pages were fetched with retries until the payload exceeded 150 KB). |
Matched |
| =PERMUT(3,2) | Microsoft's second documented row | 6 | 6ProvenanceMicrosoft publishes =PERMUT(3,2) = 6, "Permutations possible for a group of 3 objects where 2 are chosen". 3!/1! = 3 x 2 = 6, and the six orderings can be written out by hand, so this case is verifiable without arithmetic at all. |
Matched |
| =PERMUT(5,0) | Choosing zero objects, which the documented equation forces to 1 | 1 | 1Provenancen!/(n-0)! = 1 for every n: there is exactly one arrangement of nothing. Microsoft does not print this row, but the value is forced by the equation the page does print, and the page's error list explicitly permits number_chosen = 0 (it errors only "If number <= 0 or if number_chosen < 0"). The empty permutation is the classic off-by-one in a hand-rolled implementation. |
Matched |
| =PERMUT(3.9,2.9) | Fractional arguments, which the page says are truncated | 6 | 6ProvenanceMicrosoft documents: "Both arguments are truncated to integers." Truncation (not rounding) of 3.9 and 2.9 gives 3 and 2, so this must return PERMUT(3,2) = 6. An engine that ROUNDED instead would compute PERMUT(4,3) = 24 -- a four-fold difference, which makes this a decisive one-value test of the documented rule. |
Matched |
| =PERMUT(2,3) | Choosing more objects than exist, which the page excludes | #VALUE! | #NUM!ProvenanceMicrosoft documents: "If number < number_chosen, PERMUT returns the #NUM! error value." |
Mismatch |
| =PERMUT(0,0) | Zero objects, which the page excludes even when nothing is chosen | 1 | #NUM!ProvenanceMicrosoft documents: "If number <= 0 or if number_chosen < 0, PERMUT returns the #NUM! error value." Zero is the boundary the <= includes, so PERMUT(0,0) is an error even though the empty arrangement of an empty set is mathematically 1 -- and note that PERMUTATIONA, the sibling function, documents the opposite treatment of the same input. That disagreement between two Microsoft pages is itself worth pinning. EXECUTED RESULT -- A SILENT WRONG ANSWER: LibreOffice returns 1 on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3), which agree case for case, where Excel documents #NUM!. Mathematically 1 is defensible -- there is exactly one arrangement of nothing -- but it is not what Microsoft's page specifies, and the disagreement is invisible: no error, no warning, just a number where Excel gives an error. Note that LibreOffice is here MORE permissive than Excel, the opposite direction from most of this batch's divergences. |
Mismatch |
| =PERMUT("x",2) | A non-numeric argument | #VALUE! | #VALUE!ProvenanceMicrosoft documents: "If number or number_chosen is nonnumeric, PERMUT returns the #VALUE! error value." |
Matched |
Docs & syntax
- Excel (desktop): official documentation
- Google Sheets: official documentation
- LibreOffice Calc: official documentation