← All functions

AVERAGE.WEIGHTED

Unsupported (not recognized)

Category: Statistical · Last tested 2026-09-01

Real compatibility results for the AVERAGE.WEIGHTED function: executed in Excel for the web, Google Sheets and LibreOffice Calc, measured against Google’s published documentation. Excel does not document AVERAGE.WEIGHTED, 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 AVERAGE.WEIGHTED’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 AVERAGE.WEIGHTED working in LibreOffice?

LibreOffice Calc does not implement AVERAGE.WEIGHTED 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
=ROUND(AVERAGE.WEIGHTED(A1:A2, B1:B2),10) Published example-table row 1: two values and two weights taken from ranges #NAME? 3.5
Provenance

GOOGLE'S OWN PUBLISHED RESULT, from the Formula/Result table in the article body: =AVERAGE.WEIGHTED(A1:A2, B1:B2) -> 3.5, over the table's own data (A1=2, A2=4, A3=8, B1=1, B2=3, B3=6). Derived independently as (2*1 + 4*3)/(1+3) = 14/4 = 3.5. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098. 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.

Mismatch
=ROUND(AVERAGE.WEIGHTED(2, 10, 4, 15),10) Published row 2: values and weights given inline rather than as ranges #NAME? 3.2
Provenance

GOOGLE'S OWN PUBLISHED RESULT: =AVERAGE.WEIGHTED(2, 10, 4, 15) -> 3.2. Derived independently as (2*10 + 4*15)/(10+15) = 80/25 = 3.2. This row is what fixes the ARGUMENT ORDER as value, weight, value, weight -- the syntax line alone (values, weights, [additional values], [additional weights]) could be read the other way. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Mismatch
=ROUND(AVERAGE.WEIGHTED(A1:A2, B1:B2, A3, B3),10) Published row 3's result, with the cell references its own table contradicts #NAME? 6.2
Provenance

THE PUBLISHED FORMULA IN THIS ROW CANNOT PRODUCE THE PUBLISHED ANSWER, AND THE PAGE'S OWN LAYOUT SHOWS WHY. Google prints "=AVERAGE.WEIGHTED(A1:A2, B1:B2, C1, C2)" -> 6.2. But in that same example table column C is the FORMULA column and column D the RESULT column: C1 holds the header word "Formula" and C2 holds the first example formula. A weighted average cannot take a header string as an additional value and another formula as its weight. The data the row must have meant is the third row of the table's own data block, A3=8 and B3=6, and that reproduces the published figure exactly: (2*1 + 4*3 + 8*6)/(1+3+6) = 62/10 = 6.2. This case therefore asserts Google's published RESULT through the references its data requires, and records the printed references as wrong. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Mismatch
=ROUND(AVERAGE.WEIGHTED(B2:B6, C2:C6),10) Published second example: a course grade weighted by percentage of final grade #NAME? 87.7
Provenance

GOOGLE'S OWN PUBLISHED RESULT from the page's second example table: =AVERAGE.WEIGHTED(B2:B6, C2:C6) -> 87.7, over grades 95/90/85/88/82 weighted 25%/10%/15%/20%/30%. Derived independently as 23.75 + 9 + 12.75 + 17.6 + 24.6 = 87.7. The percentages are stored here as the numbers 0.25 ... 0.3, which is what a cell displaying "25%" contains. This is the only published example whose weights sum to exactly 1. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Mismatch
=ROUND(AVERAGE.WEIGHTED(A1:A3, C1:C3),10) A zero weight, which the argument description explicitly permits #NAME? 5
Provenance

DERIVED from the `weights` argument description: "Weights cannot be negative, though they can be zero. At least one of the weights must be positive." A zero weight must therefore drop its value out of both the numerator and the denominator: (2*1 + 4*0 + 8*1)/(1+0+1) = 10/2 = 5. Google publishes no example with a zero weight and names NO error value for a negative weight, so this corpus asserts nothing about negative weights. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

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
=ROUND(AVERAGE.WEIGHTED(A1:A2, B1:B2),10) Published example-table row 1: two values and two weights taken from ranges 3.5 3.5
Provenance

GOOGLE'S OWN PUBLISHED RESULT, from the Formula/Result table in the article body: =AVERAGE.WEIGHTED(A1:A2, B1:B2) -> 3.5, over the table's own data (A1=2, A2=4, A3=8, B1=1, B2=3, B3=6). Derived independently as (2*1 + 4*3)/(1+3) = 14/4 = 3.5. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098. 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.

Matched
=ROUND(AVERAGE.WEIGHTED(2, 10, 4, 15),10) Published row 2: values and weights given inline rather than as ranges 3.2 3.2
Provenance

GOOGLE'S OWN PUBLISHED RESULT: =AVERAGE.WEIGHTED(2, 10, 4, 15) -> 3.2. Derived independently as (2*10 + 4*15)/(10+15) = 80/25 = 3.2. This row is what fixes the ARGUMENT ORDER as value, weight, value, weight -- the syntax line alone (values, weights, [additional values], [additional weights]) could be read the other way. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Matched
=ROUND(AVERAGE.WEIGHTED(A1:A2, B1:B2, A3, B3),10) Published row 3's result, with the cell references its own table contradicts 6.2 6.2
Provenance

THE PUBLISHED FORMULA IN THIS ROW CANNOT PRODUCE THE PUBLISHED ANSWER, AND THE PAGE'S OWN LAYOUT SHOWS WHY. Google prints "=AVERAGE.WEIGHTED(A1:A2, B1:B2, C1, C2)" -> 6.2. But in that same example table column C is the FORMULA column and column D the RESULT column: C1 holds the header word "Formula" and C2 holds the first example formula. A weighted average cannot take a header string as an additional value and another formula as its weight. The data the row must have meant is the third row of the table's own data block, A3=8 and B3=6, and that reproduces the published figure exactly: (2*1 + 4*3 + 8*6)/(1+3+6) = 62/10 = 6.2. This case therefore asserts Google's published RESULT through the references its data requires, and records the printed references as wrong. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Matched
=ROUND(AVERAGE.WEIGHTED(B2:B6, C2:C6),10) Published second example: a course grade weighted by percentage of final grade 87.7 87.7
Provenance

GOOGLE'S OWN PUBLISHED RESULT from the page's second example table: =AVERAGE.WEIGHTED(B2:B6, C2:C6) -> 87.7, over grades 95/90/85/88/82 weighted 25%/10%/15%/20%/30%. Derived independently as 23.75 + 9 + 12.75 + 17.6 + 24.6 = 87.7. The percentages are stored here as the numbers 0.25 ... 0.3, which is what a cell displaying "25%" contains. This is the only published example whose weights sum to exactly 1. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Matched
=ROUND(AVERAGE.WEIGHTED(A1:A3, C1:C3),10) A zero weight, which the argument description explicitly permits 5 5
Provenance

DERIVED from the `weights` argument description: "Weights cannot be negative, though they can be zero. At least one of the weights must be positive." A zero weight must therefore drop its value out of both the numerator and the denominator: (2*1 + 4*0 + 8*1)/(1+0+1) = 10/2 = 5. Google publishes no example with a zero weight and names NO error value for a negative weight, so this corpus asserts nothing about negative weights. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Matched

LibreOffice Calc 25.8.7.3 (tested 2026-09-01)

FormulaDescriptionResultExpectedVerdict
=ROUND(AVERAGE.WEIGHTED(A1:A2, B1:B2),10) Published example-table row 1: two values and two weights taken from ranges #NAME? 3.5
Provenance

GOOGLE'S OWN PUBLISHED RESULT, from the Formula/Result table in the article body: =AVERAGE.WEIGHTED(A1:A2, B1:B2) -> 3.5, over the table's own data (A1=2, A2=4, A3=8, B1=1, B2=3, B3=6). Derived independently as (2*1 + 4*3)/(1+3) = 14/4 = 3.5. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098. 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.

Mismatch
=ROUND(AVERAGE.WEIGHTED(2, 10, 4, 15),10) Published row 2: values and weights given inline rather than as ranges #NAME? 3.2
Provenance

GOOGLE'S OWN PUBLISHED RESULT: =AVERAGE.WEIGHTED(2, 10, 4, 15) -> 3.2. Derived independently as (2*10 + 4*15)/(10+15) = 80/25 = 3.2. This row is what fixes the ARGUMENT ORDER as value, weight, value, weight -- the syntax line alone (values, weights, [additional values], [additional weights]) could be read the other way. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Mismatch
=ROUND(AVERAGE.WEIGHTED(A1:A2, B1:B2, A3, B3),10) Published row 3's result, with the cell references its own table contradicts #NAME? 6.2
Provenance

THE PUBLISHED FORMULA IN THIS ROW CANNOT PRODUCE THE PUBLISHED ANSWER, AND THE PAGE'S OWN LAYOUT SHOWS WHY. Google prints "=AVERAGE.WEIGHTED(A1:A2, B1:B2, C1, C2)" -> 6.2. But in that same example table column C is the FORMULA column and column D the RESULT column: C1 holds the header word "Formula" and C2 holds the first example formula. A weighted average cannot take a header string as an additional value and another formula as its weight. The data the row must have meant is the third row of the table's own data block, A3=8 and B3=6, and that reproduces the published figure exactly: (2*1 + 4*3 + 8*6)/(1+3+6) = 62/10 = 6.2. This case therefore asserts Google's published RESULT through the references its data requires, and records the printed references as wrong. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Mismatch
=ROUND(AVERAGE.WEIGHTED(B2:B6, C2:C6),10) Published second example: a course grade weighted by percentage of final grade #NAME? 87.7
Provenance

GOOGLE'S OWN PUBLISHED RESULT from the page's second example table: =AVERAGE.WEIGHTED(B2:B6, C2:C6) -> 87.7, over grades 95/90/85/88/82 weighted 25%/10%/15%/20%/30%. Derived independently as 23.75 + 9 + 12.75 + 17.6 + 24.6 = 87.7. The percentages are stored here as the numbers 0.25 ... 0.3, which is what a cell displaying "25%" contains. This is the only published example whose weights sum to exactly 1. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Mismatch
=ROUND(AVERAGE.WEIGHTED(A1:A3, C1:C3),10) A zero weight, which the argument description explicitly permits #NAME? 5
Provenance

DERIVED from the `weights` argument description: "Weights cannot be negative, though they can be zero. At least one of the weights must be positive." A zero weight must therefore drop its value out of both the numerator and the denominator: (2*1 + 4*0 + 8*1)/(1+0+1) = 10/2 = 5. Google publishes no example with a zero weight and names NO error value for a negative weight, so this corpus asserts nothing about negative weights. Google's AVERAGE.WEIGHTED page, read live on 2026-08-31 at https://support.google.com/docs/answer/9084098.

Mismatch

Docs & syntax

Where AVERAGE.WEIGHTED behaves differently