Contact

Zoho Sheet HARMEAN Function: Harmonic Mean and Average Speed

Statistical Intermediate Zoho Sheet

Calculate the harmonic mean in Zoho Sheet with equal-distance speed examples, input checks and an explained discrepancy in the official examples.

Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in Zoho Sheet. How formula examples are checked

Quick answer: =HARMEAN(A2:A5) returns a harmonic mean of the values in the specified range. If A2:A5 contain 2, 4, 8 and 16, the independently calculated mathematical expectation is 4.266666667. The harmonic mean is useful for certain kinds of ratios and rates, particularly the average speed over equal-distance segments, where using an ordinary arithmetic mean would overstate the actual overall speed.

It is important to name both the numerator and denominator of a rate before using HARMEAN. The harmonic mean is not a universal replacement for AVERAGE and should not be applied automatically to unequal-distance segments, percentages or arbitrary business KPIs.

Official Zoho Sheet syntax and parameters

HARMEAN(number; [number1]; ...)

Parameter: number

Required
Yes

Meaning
Numeric value or cell/range containing observations to average harmonically.

Example
A2:A5

Parameter: [number1]` and subsequent arguments

Required
Optional

Meaning
Additional numeric values, references or ranges contributing to the mean.

Example
B2:B10 or 12

Zoho’s current official statistical-function reference prints arguments separated by semicolons. For example, =HARMEAN(30;60) supplies two numbers, whereas =HARMEAN(B2:B4) supplies one range argument. Use the colon for contiguous ranges and the document’s displayed separator convention for multiple arguments. Do not assume every Excel or Google Sheets locale uses the same separator.

The Zoho Sheet online catalogue includes HARMEAN. The official function reference does not establish a first supported release or guaranteed parity across all historical/mobile/desktop versions. The 2026 Zoho beta desktop announcement says many built-in functions are present, but the specific behaviour and edge cases of HARMEAN have not been verified there.

What is a harmonic mean?

For n strictly positive numbers x1, x2, ..., the harmonic mean is:

H = n / (1/x1 + 1/x2 + ... + 1/xn)

It is the reciprocal of the arithmetic mean of the reciprocals. Small observations matter more than they would under an arithmetic mean, because their reciprocals are larger.

The harmonic mean, geometric mean and arithmetic mean form a useful sequence for the same set of strictly positive values: harmonic ≤ geometric ≤ arithmetic. Equality occurs when every included value is the same. This relationship is a mathematical quality check; it is not a claim that we successfully executed these functions in Zoho Sheet.

Example 1: a reproducible four-value calculation

Enter the following sample data into a new Zoho worksheet:

Cell Data
A1 Observation
A2 2
A3 4
A4 8
A5 16
  1. Select C2 and enter =HARMEAN(A2:A5).
  2. The independently calculated expected result is 4.266666667.
  3. Check the reciprocals: 1/2 = 0.5, 1/4 = 0.25, 1/8 = 0.125, and 1/16 = 0.0625. Their sum is 0.9375.
  4. Divide the observation count 4 by that sum: 4/0.9375 = 4.266666667.
  5. In C3 enter =GEOMEAN(A2:A5). Its mathematical expected output is 5.656854249. In C4 enter =AVERAGE(A2:A5); the expected output is 7.5.

Those three values illustrate why a statement such as “the dataset has an average of five” is ambiguous unless the type of mean is specified. Each calculation answers a different question.

On its HARMEAN reference page, Zoho displays =HARMEAN(1;2;3;4;5) → 9.901768173. This is not mathematically consistent with the standard harmonic-mean definition: five strictly positive values between 1 and 5 must have a harmonic mean between 1 and 5. Independent calculation gives:

5 / (1 + 1/2 + 1/3 + 1/4 + 1/5) = 2.189781021898

The vendor example exceeds the largest input. This guide records a documented example discrepancy, not proof of a Zoho software bug. The displayed vendor value might be a stale or incorrectly paired example. Actual native Zoho execution is required before asserting what the application returns. For that reason, this guide uses transparent arithmetic and explicitly labels expected outputs as not natively tested.

Example 2: average speed across equal distances

Suppose a delivery vehicle drives three equal 30-km legs at different speeds. In a sheet, enter:

Row: 1

A: Route leg
Leg

B: Speed (km/h)
Speed

C: Distance (km)
Distance

D: Time (hours)
Time

Row: 2

A: Route leg
1

B: Speed (km/h)
30

C: Distance (km)
30

D: Time (hours)
=C2/B2

Row: 3

A: Route leg
2

B: Speed (km/h)
60

C: Distance (km)
30

D: Time (hours)
=C3/B3

Row: 4

A: Route leg
3

B: Speed (km/h)
90

C: Distance (km)
30

D: Time (hours)
=C4/B4

  1. In D2 type =C2/B2 and fill down to D4. The mathematically expected times are 1, 0.5 and 0.333333333 hours.
  2. In F2, enter =HARMEAN(B2:B4). The independently calculated expected harmonic mean is 49.090909091 km/h.
  3. Cross-check with total distance divided by total time: =SUM(C2:C4)/SUM(D2:D4). This is 90/(1+0.5+1/3) = **49.090909091 km/h**.
  4. Compare the simple arithmetic average: =AVERAGE(B2:B4) gives 60 km/h mathematically. That is not the overall speed across equal-distance legs, because the vehicle spends more time traveling at 30 km/h than at 90 km/h.
  5. Optionally verify via =3/(1/B2+1/B3+1/B4), which has the same independent mathematical expectation as HARMEAN.

All formulas above have the same conceptual units only if distances are in kilometres, speeds in kilometres per hour and times in hours. A label such as “km/h” does not emerge from a plain number automatically; set the number format and dashboard label appropriately.

Advanced application: why unequal distances change the answer

The simple harmonic mean of 30, 60 and 90 km/h is correct for the equal-distance scenario above. Now change distances to 30 km, 60 km and 90 km while keeping those speeds:

Speed Distance Time
30 km/h 30 km 1 hour
60 km/h 60 km 1 hour
90 km/h 90 km 1 hour

The correct overall speed is total distance / total time = 180 km / 3 hours = 60 km/h, not 49.090909091 km/h. Therefore do not use unweighted HARMEAN for unequal-distance legs. Instead calculate a total-distance-over-total-time ratio from the original rows.

In a flexible route worksheet where B2:B4 holds speeds and C2:C4 holds distances, let D2 be =C2/B2 and fill down. Compute =SUM(C2:C4)/SUM(D2:D4) for the distance-weighted travel speed, handling any zero speeds or inconsistent units before dividing.

HARMEAN can also be applicable to averages of rates expressed per a common numerator or denominator unit, but conditions matter. For example, some financial price-to-earnings averages require fundamentally different weighting and careful treatment of zero/negative ratios. Do not label a generic unweighted HARMEAN as a correct portfolio or aggregate ratio without deriving the appropriate weights.

Troubleshooting, invalid values and limits

Symptom What Zoho actually documents or what remains unknown Suggested action
#NUM! Zoho’s HARMEAN error table specifically says a supplied number less than zero can cause this error. Remove invalid negative rate observations or use an analysis suited to signed data.
Zero speed / zero input The vendor page does not separately document its zero boundary, while the reciprocal mathematical formula is undefined at zero and Excel explicitly rejects nonpositive values. Treat zero as a validation hold. Verify the actual Zoho result in the native app; do not divide by zero manually.
#VALUE! The documented generic explanation is an invalid argument data type. Inspect imported text numerals, malformed percentage strings and cells formatted as numbers but storing text.
#NAME! Wrong function or defined name, missing text quotes, or a malformed range expression. Verify spelling, semicolons and : in ranges.
#REF! Missing or invalid referenced cells. Replace broken source references.
#N/A! Listed in Zoho’s generic error table, but this function is not a lookup. Trace the upstream referenced cells instead of assuming HARMEAN performs a search.
Result larger than the maximum positive input Violates the mathematical bounds for a standard harmonic mean. Audit the source and denominator. The official 1–5 example itself needs a vendor/native check.
Rates based on different distances or weights The simple harmonic formula may not measure the aggregate you want. Derive total numerator and denominator before selecting a mean type.

The exact treatment of blank cells, text, Boolean values, error values and numeric strings in Zoho cannot be established from the short function-specific reference alone. Excel documents specific coercion rules, but those are not a substitute for a Zoho test. Likewise, the native result for an empty range or a zero-valued input should not be invented from a general error table.

A simple candidate input guard when B2:B4 should contain exactly three numeric positive speeds is:

=IF(OR(COUNT(B2:B4)<>3;MIN(B2:B4)<=0);"Review input";HARMEAN(B2:B4))

This is a reasoned spreadsheet pattern, not a native Zoho-tested expression. It assumes IF, OR, COUNT and MIN work as separately documented and all three input cells belong to the intended dataset. In particular, COUNT excludes text in typical numeric counting; this guard deliberately flags a nonnumeric entry by comparing the count with 3. Before publishing a guaranteed behaviour claim, execute the guard against bad data in Zoho.

Cross-software differences and alternatives

  • Microsoft Excel documents HARMEAN(number1, [number2], ...) and explicitly defines the function as the reciprocal of the arithmetic mean of reciprocals. Excel’s support page states that a nonpositive point produces #NUM!, and explains when text, Booleans or blank cells inside references are ignored. This does not establish the same coercion or zero-error rules for Zoho.
  • Google Sheets documents HARMEAN(value1, [value2, ...]), with sample English formulas separated by commas. Its explanation uses the population count divided by the sum of reciprocals, and it supplies no guarantee of identical parsing in Zoho.
  • Arithmetic AVERAGE is usually suitable when observations contribute equally by quantity or time, whereas harmonic averaging is mathematically appropriate for equal-distance speeds. For arbitrary distances, using total distance / total time is more defensible than changing a function name.
  • GEOMEAN handles equally weighted multiplicative factors such as period-by-period growth, not speed across fixed distances. With positive values it normally lies between HARMEAN and AVERAGE.

This proposal is editorial research for Spreadsheet-Tutorials.com, not a published guide. Official Zoho function references were inspected on October 12, 2026. Numeric outcomes are calculated independently in Python using elementary arithmetic; none has been executed in Zoho Sheet. The cited current English web documentation supplies no reliable first-supported version, licensing matrix, or guarantee of identical behavior in every mobile, historical, or beta desktop build. Formula outcomes should be tested in a native Zoho Sheet worksheet before editorial approval.

  • GEOMEAN — continue with a related Zoho Sheet calculation.
  • AVERAGE — continue with a related Zoho Sheet calculation.
  • MEDIAN — continue with a related Zoho Sheet calculation.

For a software-specific comparison: LibreOffice Calc HARMEAN. A shared name does not establish identical argument, error or version behaviour.

How this guide was checked

The linked official Zoho Sheet function documentation was reviewed on October 12, 2026. Cloud documentation does not establish feature parity across historical clients. Selected worked examples were checked using independent mathematical or text-processing models; results are expected values, not observations from the spreadsheet application. Native Zoho Sheet execution was not performed. Undocumented coercion, exact error messages and platform-specific behaviour remain unverified.

View reproducible example inputs and independent check results. This record is not a native spreadsheet test log.