EV/EBITDA Calculator
The formula
What the ev/ebitda tells you
How many years of operating cash earnings the whole business is priced at — the workhorse multiple for acquisitions and leveraged finance.
Calculation: EV/EBITDA = enterprise value ÷ EBITDA. Enter your inputs and every substitution is shown below the result.
Reading the result
Compare only within an industry and cycle position: 8× for a cyclical at peak earnings is not the same bargain as 8× for a compounder.
Rules of thumb: US market median ~9–11×; LBO range 5–8×; software 15–25×
Limitations and best practice
The denominator is the game — one-off addbacks and capitalized costs inflate EBITDA and collapse the multiple without any real cheapness.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Why EV/EBITDA instead of P/E?
What multiple is a good deal?
Source & methodology
Standard valuation multiple; ranges from Capital IQ and Kroll deal surveys.
EV/EBITDA explained: formula, worked example and honest limits
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. EV/EBITDA is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get EV/EBITDA in real time, and see every substitution printed below.
In plain terms, EV/EBITDA answers the question "EV/EBITDA?". The measurement matters because it converts a situation that feels complicated — several inputs pulling in different directions — into a single number you can act on. Within Business & Entrepreneurship, Financial Analysis is the context where this figure is quoted most often, and professionals treat it as a first-pass screen rather than a verdict.
Business runs on numbers that are cheap to compute and expensive to ignore. EV/EBITDA in Business & Entrepreneurship is one of those: EV/EBITDA = enterprise value ÷ EBITDA, and the gap between founders who check and founders who hope shows up exactly here.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to EV/EBITDA = 7.5 × on the default inputs, and the sensitivity section ranks the inputs that move the result — EBITDA first, at ≈11.1 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.
How EV/EBITDA is computed, line by line
The engine implements a single stated model: EV/EBITDA = enterprise value ÷ EBITDA. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Enterprise value ($) (example value 6,475,000) is a quantity rather than a category — precision here is cheap and worth having. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
EBITDA ($) (example value 857,933) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
EV/EBITDA with real numbers, step by step
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Enterprise value ($), EBITDA ($). The endpoint of that chain is 7.5 × of EV/EBITDA, sitting in the “Normal corporate trading band” band.
- EV/EBITDA = $6,475,000 ÷ $857,933 = 7.5×
- This is the multiple acquisition committees actually argue over
Years of EBITDA in the price — 7.5. Compare it against the main result of 7.5 × before drawing conclusions.
EBITDA yield (inverse) — 13.2 %. Compare it against the main result of 7.5 × before drawing conclusions.
EV that 10× would imply — $8,579,330. Compare it against the main result of 7.5 × before drawing conclusions.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
The EV/EBITDA corridor: your result across a realistic band
The honest version of any estimate is a corridor, and this one is cheap to produce: EV/EBITDA was recomputed at 5 points along the dominant input, with every other field left untouched.
| EBITDA setting | EV/EBITDA |
|---|---|
| 80 % of the example value | 9.4 × |
| 90 % of the example value | 8.4 × |
| example inputs | 7.5 × |
| 110 % of the example value | 6.9 × |
| 120 % of the example value | 6.3 × |
Across 5 settings of EBITDA, the result spans 6.3 × to 9.4 ×. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing EBITDA alone; the substitution steps will follow your figures exactly.
Where EV/EBITDA is fragile — and where it is not
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the EV/EBITDA recomputed, so the ranking below is measured rather than asserted. Read it as a map of where EV/EBITDA is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- EBITDA +10 % → EV/EBITDA = 6.9 × · −10 % → 8.4 × (the EV/EBITDA shifts ≈11.1 %)
- Enterprise value +10 % → EV/EBITDA = 8.3 × · −10 % → 6.8 × (the EV/EBITDA shifts ≈10.0 %)
EBITDA is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 6.9 × to 8.4 ×. That is where a careless figure does the most damage, so check it against a source, and treat Enterprise value as the second priority (≈10.0 % per ten percent). The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
Is your EV/EBITDA good — reading the result bands
A number on its own is trivia; a number against a range is intelligence. The verdict attached to the default calculation — “Normal corporate trading band” — is one band on a ladder your own figure may sit somewhere else on. How much of that band is luck? On EBITDA alone ten percent either way covers 6.9 × to 8.4 ×. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
Related measures answer related questions, and the distinctions matter: EV/EBITDA is the quantity, EV/EBITDA is this tool’s reading of it, and the decision that follows belongs to neither of them separately.
Why EV/EBITDA results go wrong — and how to prevent it
The denominator is the game — one-off addbacks and capitalized costs inflate EBITDA and collapse the multiple without any real cheapness. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Leaving a line out of the input. An omitted fee, tax or headcount is not a rounding error — it is a structural optimism bias.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows EBITDA dominating — a careful figure there beats false precision everywhere else.
The subtlest error is answering the wrong question precisely. Confirm that EV/EBITDA is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
A quick check for any EV/EBITDA figure
- Compare the output against one published benchmark or a colleague’s independent estimate.
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- Check EBITDA before anything else: it is the measured dominant input, ≈11.1 % of EV/EBITDA per ten percent.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Verify each input against its original source document, not memory.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
How to use the EV/EBITDA tool properly
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for EV/EBITDA takes a minute to learn and applies to every input above.
Step 1 — start from evidence. The inputs behind EV/EBITDA are enterprise value ($), ebitda ($). Write them down with their source next to each one; if you cannot name where a figure came from, that is the input most likely to be wrong. The inputs are the part of the work that nobody else can do for you.
Step 2 — baseline before exploration. Get one defensible EV/EBITDA on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. A calculation you cannot explain to somebody else is a calculation you cannot defend.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. Rounding early is the quietest way to introduce a permanent error.
Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. A result worth acting on survives having its two shakiest inputs halved.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 7.5 ×, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. Precision is a promise you make about your data; make sure your inputs can keep it.
The real-world conversations EV/EBITDA settles
In Financial Analysis the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
The audience for this page is people who need one trustworthy number before their next decision. In professional Financial Analysis practice the pattern is always the same — screen with EV/EBITDA, then invest slow analysis only in whatever survives the screen. Half of a good calculation is knowing which input you would hate to be wrong about.
Treat EV/EBITDA like a smoke alarm rather than a painting — its value is in being tested periodically, not in being admired once. The point of transparency is that a reader can disagree with a specific line rather than with you.
Quick answers: what searchers ask about EV/EBITDA
What affects EV/EBITDA the most?
The short answer: EBITDA. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the EV/EBITDA recalculated — EBITDA moved it furthest, by roughly 11.1 % (6.9 × to 8.4 ×).
Which matters more: enterprise value or ebitda?
EBITDA, by a factor of about 1.1. Concretely: ten percent on EBITDA is worth ≈11.1 % of EV/EBITDA, the same nudge on Enterprise value only ≈10.0 %. That ranking is re-computed for each page from that page’s own defaults.
What is a typical EV/EBITDA?
There is no honest universal average for EV/EBITDA, but there is a reference point: the defaults on this page produce 7.5 × (Normal corporate trading band). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate EV/EBITDA by hand?
EV/EBITDA = enterprise value ÷ EBITDA is the entire method. Work the inputs in that order — EV/EBITDA = $6,475,000 ÷ $857,933 = 7.5× — and you will reach 7.5 × on the default figures, the same number this tool prints.
What happens to EV/EBITDA if ebitda changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 6.9 × to 8.4 × across the ten-percent probe, i.e. ≈11.1 % sensitivity on the EV/EBITDA.
Is the EV/EBITDA result of 7.5 × good or bad?
Neither, on its own — the label “Normal corporate trading band” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in EBITDA alone moves it by ≈11.1 %.
What does 7.5 × tell me about the business?
It answers the narrow question mechanically and the broad question only in context: EV/EBITDA is one dashboard light, and it pairs with unit economics and cash timing before any bet the business size.
Is EV/EBITDA accurate?
The arithmetic is exact: EV/EBITDA = enterprise value ÷ EBITDA is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 7.5 × result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Why EV/EBITDA instead of P/E?
It neutralizes capital structure and tax differences, letting two companies financed entirely differently sit on the same chart.
What multiple is a good deal?
Deal multiples cluster at 5–8× for middle-market industrial services and 12–20× for software; the right answer is always relative to growth and durability.
Can this tool see the numbers I type?
It cannot. There is no submission step: the calculation happens in your browser and the result disappears when you close the page. Treat the fields above as a scratchpad rather than a form.
The vocabulary of EV/EBITDA
- Years of EBITDA in the price
- 7.5 in the default EV/EBITDA calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- EBITDA yield (inverse)
- 13.2 % on the example inputs — a companion figure printed beside the headline of EV/EBITDA so that no result is read in isolation.
- EV that 10× would imply
- $8,579,330 on the example inputs — a companion figure printed beside the headline of EV/EBITDA so that no result is read in isolation.
- EV/EBITDA
- The primary output of this tool: 7.5 × for the default inputs, computed exactly from EV/EBITDA = enterprise value ÷ EBITDA.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The plain-language label — here “Normal corporate trading band” — mapping the computed figure onto experience-based ranges for Business & Entrepreneurship.
- Sensitivity (±10 %)
- How far the EV/EBITDA moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
The provenance of this EV/EBITDA calculation
The model is published arithmetic implemented exactly as written: EV/EBITDA = enterprise value ÷ EBITDA. Source of record: Standard valuation multiple; ranges from Capital IQ and Kroll deal surveys. Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
Turning this EV/EBITDA into a decision
Save the number together with its inputs and today’s date; an EV/EBITDA figure without context is unusable the moment an input changes.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.