Contact
12 programs
Explore the site

INTERCEPT in Zoho Sheet: Regression Y-Intercept Examples

Statistical Intermediate Zoho Sheet

Find where a Zoho Sheet least-squares trendline crosses the y-axis, with paired weekly-data 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: INTERCEPT gives the predicted Y value at X = 0 for a least-squares straight line fitted to paired numeric observations. For the six-week sample below, =INTERCEPT(B2:B7;A2:A7) has the independently derived expected value 1.666666667. This is the line’s mathematical Y-axis crossing—not necessarily an observed value or a realistic business baseline. Zoho documents the dependent Y range first and independent X range second. Zoho INTERCEPT help, checked October 12, 2026.

Official syntax and argument order

=INTERCEPT(y_values; x_values)
Argument Required? Function
y_values Yes Dependent Y observations, e.g. B2:B7 — the results you measured.
x_values Yes Independent X observations, e.g. A2:A7 — the predictor or period number.

No optional arguments or default ranges are documented. Zoho’s page defines both arguments as observed datasets and provides a generic possible-error table, but does not explicitly enumerate every numeric/text/blank pairing rule for this function. The numerical worked examples use completely numeric, equal-size ranges to avoid unverified coercion. The result is a number in units of Y, even when no X=0 row was observed. Source: Zoho INTERCEPT function help, checked 2026-10-12.

Reproduce the six-week example

  1. Create a blank sheet, then enter the following values in A1:B7.
  2. Confirm both data columns contain actual numeric cells and the two ranges are the same height.
  3. Enter the formula in a separate unused cell such as D2; do not place a formula inside its own source ranges.
  4. Display enough decimal places to compare with the expected result. Cell formatting can round the display without changing underlying values.
Row A — Week (x) B — Orders (y)
1 Week Orders
2 1 3
3 2 5
4 3 4
5 4 8
6 5 7
7 6 10

All six rows represent paired observations: week 1 corresponds to 3 orders, week 2 to 5 orders, and so on. Keep the header row outside the input ranges. Do not sort only one column; doing so destroys the pairings. Check that A2:B7 are numeric, with no text-number import problems.

Worked example 1 — Calculate the Y-axis crossing

Enter in D3:

=INTERCEPT(B2:B7;A2:A7)

Expected result: 1.666666666666667 (often displayed as 1.666666667). The fitted regression equation is Å· = 1.666666667 + 1.285714286x. Setting x to zero gives approximately 1.667 orders. Because the observed weeks start at 1, this value is an extrapolated mathematical intercept, not a recorded pre-launch order count.

Check independently

For a simple least-squares line with a free intercept, let x̄ and ȳ be the numeric means of the paired observations. Then

  • xÌ„ = 3.5, ȳ = 37/6 = 6.166666667.
  • Sxx = Σ(x − xÌ„)² = 17.5.
  • Sxy = Σ(x − xÌ„)(y − ȳ) = 22.5.
  • Syy = Σ(y − ȳ)² = 209/6 ≈ 34.833333333.
  • Least-squares slope b = Sxy/Sxx = 9/7 ≈ 1.285714286.
  • Fitted y-axis intercept a = ȳ − b×xÌ„ = 5/3 ≈ 1.666666667.
  • Correlation squared r² = Sxy²/(Sxx×Syy) = 1215/1463 ≈ 0.830485304.

These figures were computed independently from the listed numbers. They are expected mathematical values, not output obtained from a native Zoho Sheet session. The agreement between the formulas is a useful cross-check only when every formula uses exactly the same paired numeric rows.

The intercept formula is a = ȳ − b × x̄. Substituting the independently calculated means and slope gives 37/6 − (9/7)×(7/2) = 5/3. If you accidentally swap x and y in the function call, the result describes a different line; the intercept is not symmetric in the two variables.

Worked example 2 — A regression with an exact intercept

In F2:F5, enter 1, 2, 3, 4 as X values, and in G2:G5 enter 3, 5, 7, 9 as their paired Y values. The exact relationship is y = 2x + 1. Use:

=INTERCEPT(G2:G5;F2:F5)

Expected result: 1. A matching =SLOPE(G2:G5;F2:F5) has an independently calculated expected value of 2. The two results together reconstruct the original line. This exact-data sanity check is useful before applying the function to messy imported records.

Worked example 3 — An intercept outside the observed range

In J2:J6, enter independent X values 1, 2, 3, 4, 5, and in K2:K6 enter Y values 11, 9, 8, 6, 4. Then:

=INTERCEPT(K2:K6;J2:J6)

Expected result: 12.7. The independent slope is −1.7, yielding ŷ = 12.7 − 1.7x. Notice that 12.7 lies above the largest observed Y value of 11. This is not an error: the intercept refers to X=0, which was not among the entered rows.

Advanced application — Estimate a planning baseline and next period

Enter the future period number 7 into A8. Put the trend estimate into B8 or an empty report cell:

=INTERCEPT(B2:B7;A2:A7)+SLOPE(B2:B7;A2:A7)*A8

Expected result: 10.666666667. For an easily displayed planning estimate:

=ROUND(INTERCEPT(B2:B7;A2:A7)+SLOPE(B2:B7;A2:A7)*A8;2)

Expected result: 10.67. If the business wants week 8, set A8 to 8 instead, producing 11.952380952 before rounding. The fixed historical A2:B7 input is deliberately not extended to include predicted values: mixing predictions back into the training observations would contaminate the comparison.

Another documented alternative is FORECAST(7;B2:B7;A2:A7) using Zoho’s FORECAST(new_x_value; y_values; x_values) syntax. It is conceptually a one-call straight-line prediction, but native equality with the combined example has not been tested here. Zoho FORECAST, checked 2026-10-12. Forecasts should be qualified when the X=0 baseline or future X value is outside the observed range. Seasonal patterns, threshold behaviour and structural breaks are not captured by a simple straight line.

Troubleshooting and edge cases

Issue How to investigate
#NAME! Zoho’s general error table flags invalid function names/defined names. Check the spelling and any named ranges.
#REF! A deleted or moved cell reference may invalidate the range; repair both ranges before recalculating.
#VALUE! Zoho lists invalid argument types. Inspect CSV-imported numerals and formula separators; do not assume text is automatically parsed.
#N/A! Zoho lists this as a possible error but does not fully specify its INTERCEPT-specific triggers; compare range lengths and numeric availability first.
Constant X range If all X values match, regression slope is mathematically underdetermined, so the ordinary intercept formula cannot be uniquely calculated. Actual Zoho error code not tested.
Different row counts The two ranges cannot express one-to-one observations when lengths differ; make their endpoints match and check for missing paired measurements. The precise native error for INTERCEPT here is unverified.
Large negative or positive intercept A line fitted far from X=0 can extrapolate to implausible baselines; this is a modeling limitation, not necessarily a syntax problem.
Blanks, text, TRUE/FALSE Zoho’s INTERCEPT article does not document every coercion/pair omission rule. For reliable analysis, build a cleaned two-column numeric dataset and keep original rows for audit.

For basic range checks, the COUNT function guide explains counting numeric cells and the AVERAGE guide explains means.

Comparison with Microsoft Excel and Google Sheets

Microsoft uses INTERCEPT(known_y's, known_x's) and Google uses INTERCEPT(data_y, data_x), matching Zoho’s Y-first meaning. Zoho’s English help uses ; while the English Microsoft and Google examples typically show ,; spreadsheet locale settings may change what you see. Microsoft discusses the possibility of a difference between Excel INTERCEPT/SLOPE and LINEST algorithms for degenerate observations, but this does not prove the Zoho engine has the same implementation or error behavior. Google’s reference says text is ignored, while Zoho’s INTERCEPT page does not fully specify mixed-type pairing, so a direct compatibility assertion would be unwarranted. Checked sources: Microsoft INTERCEPT and Google INTERCEPT, October 12, 2026.

SLOPE tells how quickly the line changes; INTERCEPT tells where it crosses X=0; RSQ describes squared Pearson correlation and says nothing about whether the slope is positive or negative. Related official Zoho function references: SLOPE, RSQ, LINEST. Their contents should be checked independently when changing the analysis.

Availability, settings, and validation scope

These instructions reflect Zoho’s English public Zoho Sheet help as checked on October 12, 2026. Its examples use semicolons (;) between arguments; a different locale or imported workbook can display a different separator. Use the formula separator accepted by your own sheet without altering the argument order. The checked function article does not give a first-supported version, a universal account/plan entitlement, or a device-by-device compatibility matrix; therefore this guide makes no such claims. Feature behaviour in older releases, mobile clients, disconnected spreadsheets and third-party imports remains unverified.

Validation ledger: Official-reference research = checked; independent mathematical model = checked; native Zoho Sheet execution = NOT RUN; actual returned error codes for edge cases = NOT RUN.

References and dates

  1. Zoho Sheet — INTERCEPT, required arguments, examples and generic errors. Checked 2026-10-12: https://help.zoho.com/portal/en/kb/sheet/functions/statistical/articles/intercept
  2. Zoho Sheet — SLOPE, linked calculation and numeric/blank guidance. Checked 2026-10-12: https://help.zoho.com/portal/en/kb/sheet/functions/statistical/articles/slope
  3. Zoho Sheet — FORECAST, linear-prediction alternative. Checked 2026-10-12: https://help.zoho.com/portal/en/kb/sheet/functions/statistical/articles/forecast-function
  4. Microsoft Excel — INTERCEPT, compatibility contrast only. Checked 2026-10-12: https://support.microsoft.com/en-us/excel/functions/intercept-function
  5. Google Sheets — INTERCEPT, compatibility contrast only. Checked 2026-10-12: https://support.google.com/docs/answer/3093632?hl=en