← All functions

GTE

Unsupported (not recognized)

Category: Operator · Last tested 2026-09-01

Real compatibility results for the GTE function: executed in Excel for the web, Google Sheets and LibreOffice Calc, measured against Google’s published documentation. Excel does not document GTE, so this page makes no claim about Excel. Syntax and links to that documentation are below.

Support matrix

EngineDocumentedLive-testedVerdict
Excel (desktop)No n/a (not an Excel function) n/a
Excel for the web— Yes (recalc, 2026-09-01) Unsupported (not recognized)
Google SheetsYes Yes (Drive import, 2026-09-01) Supported, behaves as documented
LibreOffice CalcNo Yes (25.8.7.3, 2026-09-01) Unsupported (not recognized)

LibreOffice version history

We executed the same test cases under each LibreOffice release to show exactly when GTE’s support changed — not documentation claims, real results.

LibreOffice versionVerdictTested
24.2.0.3 Unsupported (not recognized) 2026-09-01
24.8.7.2 Unsupported (not recognized) 2026-09-01
25.2.0.3 Unsupported (not recognized) 2026-09-01
25.8.7.3 Unsupported (not recognized) 2026-09-01

Why isn't GTE working in LibreOffice?

LibreOffice Calc does not implement GTE as of 25.8.7.3 — in our executed tests it returns a #NAME? (unrecognized function) error. This is not a typo or a settings problem, and saving the file as .xlsx does not change it: the function simply isn’t available yet. Watch the LibreOffice version support page — we re-run every test on each new release, so it will flip to Supported here as soon as it lands.

Discovered quirks

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.

FormulaDescriptionResultExpectedVerdict
=GTE(2,3) The page's own Sample Usage line, GTE(2,3) #NAME? False
Provenance

Google's Sample Usage prints GTE(2,3) with no result; FALSE is DERIVED from the page's one-line definition and its "Equivalent to the `>=` operator" clause. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975. BATCH PROVENANCE (batch H, the first Sheets/LibreOffice-only batch). Every function in this batch has x == false in docs/data/compat.json: it is a Google Sheets function that Microsoft does not document at all, so this corpus makes NO claim about it in that engine and nothing here is measured against that vendor's documentation. The authority is Google's own support.google.com function page, cited by full URL and by the date it was read -- Google publishes no version number for these pages, so a bare URL dates nothing. WHAT GOOGLE ACTUALLY PRINTS, WHICH IS LESS THAN IT LOOKS: most of these pages carry a 'Sample Usage' block of FORMULAS WITH NO RESULTS. Where a value below is Google's own published output the note says so; where it is derived from the page's stated semantics the note says that instead, and says from which sentence. No value in this batch was taken from a search snippet, a blog or a mirror. LIBREOFFICE: probed on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) in five storage spellings -- plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE. and _xlfn.ORG.OPENOFFICE. -- and #NAME? under every one of them, so the expected values below describe Google Sheets and the LibreOffice column records absence. THE PAGE SAYS NOTHING ABOUT TEXT. None of the six comparison-operator pages (EQ, NE, GT, GTE, LT, LTE) makes any statement about comparing text to text, text to numbers, mixed types, or case sensitivity, and none of them prints a single result value; their Examples sections are embedded live spreadsheets whose cells are not part of the article text. So this file asserts text behaviour only STRUCTURALLY -- the function must agree with the operator it is documented to be equivalent to, whatever that operator does -- and never asserts what the comparison itself yields on text.

Mismatch
=GTE(A2,A3) The page's cell-reference Sample Usage line #NAME? False
Provenance

The same comparison through cell references. The page names A2 and A3 without populating them, so this corpus chose 2 and 3 to match the literal sample. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975.

Mismatch
=GTE(5,5) The boundary the page's wording turns on: two equal values #NAME? True
Provenance

Derived from the exact wording of the definition and the `>=` equivalence. This is the case that separates GTE from its neighbours, and Google publishes no example of it. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975. The definition reads "greater than or equal to", which is what makes GTE(5,5) TRUE.

Mismatch
=GTE("b","a")=("b">="a") GTE against the `>=` operator on text arguments #NAME? True
Provenance

A STRUCTURAL assertion with no derived constant, and deliberately so: the page never says how text compares, or whether the comparison is case sensitive, so the only thing it licenses is that the function and the operator must return the SAME answer. This case asserts that agreement and nothing about the answer itself. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975.

Mismatch

Google Sheets (executed 2026-09-01 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.

FormulaDescriptionResultExpectedVerdict
=GTE(2,3) The page's own Sample Usage line, GTE(2,3) False False
Provenance

Google's Sample Usage prints GTE(2,3) with no result; FALSE is DERIVED from the page's one-line definition and its "Equivalent to the `>=` operator" clause. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975. BATCH PROVENANCE (batch H, the first Sheets/LibreOffice-only batch). Every function in this batch has x == false in docs/data/compat.json: it is a Google Sheets function that Microsoft does not document at all, so this corpus makes NO claim about it in that engine and nothing here is measured against that vendor's documentation. The authority is Google's own support.google.com function page, cited by full URL and by the date it was read -- Google publishes no version number for these pages, so a bare URL dates nothing. WHAT GOOGLE ACTUALLY PRINTS, WHICH IS LESS THAN IT LOOKS: most of these pages carry a 'Sample Usage' block of FORMULAS WITH NO RESULTS. Where a value below is Google's own published output the note says so; where it is derived from the page's stated semantics the note says that instead, and says from which sentence. No value in this batch was taken from a search snippet, a blog or a mirror. LIBREOFFICE: probed on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) in five storage spellings -- plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE. and _xlfn.ORG.OPENOFFICE. -- and #NAME? under every one of them, so the expected values below describe Google Sheets and the LibreOffice column records absence. THE PAGE SAYS NOTHING ABOUT TEXT. None of the six comparison-operator pages (EQ, NE, GT, GTE, LT, LTE) makes any statement about comparing text to text, text to numbers, mixed types, or case sensitivity, and none of them prints a single result value; their Examples sections are embedded live spreadsheets whose cells are not part of the article text. So this file asserts text behaviour only STRUCTURALLY -- the function must agree with the operator it is documented to be equivalent to, whatever that operator does -- and never asserts what the comparison itself yields on text.

Matched
=GTE(A2,A3) The page's cell-reference Sample Usage line False False
Provenance

The same comparison through cell references. The page names A2 and A3 without populating them, so this corpus chose 2 and 3 to match the literal sample. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975.

Matched
=GTE(5,5) The boundary the page's wording turns on: two equal values True True
Provenance

Derived from the exact wording of the definition and the `>=` equivalence. This is the case that separates GTE from its neighbours, and Google publishes no example of it. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975. The definition reads "greater than or equal to", which is what makes GTE(5,5) TRUE.

Matched
=GTE("b","a")=("b">="a") GTE against the `>=` operator on text arguments True True
Provenance

A STRUCTURAL assertion with no derived constant, and deliberately so: the page never says how text compares, or whether the comparison is case sensitive, so the only thing it licenses is that the function and the operator must return the SAME answer. This case asserts that agreement and nothing about the answer itself. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975.

Matched

LibreOffice Calc 25.8.7.3 (tested 2026-09-01)

FormulaDescriptionResultExpectedVerdict
=GTE(2,3) The page's own Sample Usage line, GTE(2,3) #NAME? False
Provenance

Google's Sample Usage prints GTE(2,3) with no result; FALSE is DERIVED from the page's one-line definition and its "Equivalent to the `>=` operator" clause. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975. BATCH PROVENANCE (batch H, the first Sheets/LibreOffice-only batch). Every function in this batch has x == false in docs/data/compat.json: it is a Google Sheets function that Microsoft does not document at all, so this corpus makes NO claim about it in that engine and nothing here is measured against that vendor's documentation. The authority is Google's own support.google.com function page, cited by full URL and by the date it was read -- Google publishes no version number for these pages, so a bare URL dates nothing. WHAT GOOGLE ACTUALLY PRINTS, WHICH IS LESS THAN IT LOOKS: most of these pages carry a 'Sample Usage' block of FORMULAS WITH NO RESULTS. Where a value below is Google's own published output the note says so; where it is derived from the page's stated semantics the note says that instead, and says from which sentence. No value in this batch was taken from a search snippet, a blog or a mirror. LIBREOFFICE: probed on all four pinned builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) in five storage spellings -- plain, _xlfn., COM.MICROSOFT., ORG.OPENOFFICE. and _xlfn.ORG.OPENOFFICE. -- and #NAME? under every one of them, so the expected values below describe Google Sheets and the LibreOffice column records absence. THE PAGE SAYS NOTHING ABOUT TEXT. None of the six comparison-operator pages (EQ, NE, GT, GTE, LT, LTE) makes any statement about comparing text to text, text to numbers, mixed types, or case sensitivity, and none of them prints a single result value; their Examples sections are embedded live spreadsheets whose cells are not part of the article text. So this file asserts text behaviour only STRUCTURALLY -- the function must agree with the operator it is documented to be equivalent to, whatever that operator does -- and never asserts what the comparison itself yields on text.

Mismatch
=GTE(A2,A3) The page's cell-reference Sample Usage line #NAME? False
Provenance

The same comparison through cell references. The page names A2 and A3 without populating them, so this corpus chose 2 and 3 to match the literal sample. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975.

Mismatch
=GTE(5,5) The boundary the page's wording turns on: two equal values #NAME? True
Provenance

Derived from the exact wording of the definition and the `>=` equivalence. This is the case that separates GTE from its neighbours, and Google publishes no example of it. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975. The definition reads "greater than or equal to", which is what makes GTE(5,5) TRUE.

Mismatch
=GTE("b","a")=("b">="a") GTE against the `>=` operator on text arguments #NAME? True
Provenance

A STRUCTURAL assertion with no derived constant, and deliberately so: the page never says how text compares, or whether the comparison is case sensitive, so the only thing it licenses is that the function and the operator must return the SAME answer. This case asserts that agreement and nothing about the answer itself. Google's GTE page, read live on 2026-08-31 at https://support.google.com/docs/answer/3093975.

Mismatch

Docs & syntax

Where GTE behaves differently