Defensive interval ratio calculator
Measure the cash runway in days: 365000 of liquid assets against 1000 of average daily operating expenses covers 365 days of ordinary operations, with no new revenue and no inventory sold. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Liquid assets
- 365,000
- Average daily operating expenses
- 1,000
- Defensive interval ratio
- 365
The defensive interval ratio, also called the defensive interval or basic defense interval, measures how many days an organization can keep operating from liquid resources without collecting new revenue or drawing on inventory. Given liquid assets—cash, marketable securities, and receivables—and average daily operating expenses, the identity is liquid assets divided by daily operating expenses, returned as the number of days covered. Credit analysts, treasurers, operators, and students use this liquidity score whenever they need a time-based coverage figure rather than a current-ratio snapshot. This defensive interval ratio calculator accepts those two figures, rejects a zero or negative daily-expense base instead of dividing by zero, and returns the ratio in days.
What the defensive interval ratio means and how the formula works
The defensive interval ratio answers a practical liquidity question: if inflows stop today, how many days of ordinary operations can the firm fund from assets that convert to cash without a fire sale of inventory or plant. Liquid assets are the defensive stock: cash and cash equivalents, marketable securities or short-term investments, and net accounts receivable. Inventory is left out on purpose, because converting it quickly usually means markdowns and disruption.
Average daily operating expenses is the cash-like daily burn used as the denominator: annual or period operating expenses minus non-cash charges such as depreciation and amortization, divided by the number of days in that period—commonly 365, or 360 in some bank models. The identity is defensive interval ratio equals liquid assets divided by average daily operating expenses.
A result of ninety means the liquid stock would cover ninety days of that daily burn; a result of thirty is a tighter cushion; a result of zero means the liquid stock is empty. The ratio is related to but not the same as the current ratio, the quick acid-test ratio, or an emergency-fund months-of-expenses target: those identities use current stocks over current liabilities, or household monthly expenses, not a days-of-operations cover from defensive assets.
Average daily operating expenses must be strictly greater than zero because dividing by a zero or negative daily burn is undefined for this metric. Prefer the same currency and the same reporting window for both inputs; mixing a year-end liquid stock with a mid-year daily burn is not a defensive-interval identity, it is a mixed snapshot.
Where a defensive interval ratio calculator earns its keep
Treasurers and credit officers use a defensive interval ratio calculator when peer screens need a comparable days-of-cover score across firms that differ in size, because a current ratio of two can still hide a thin cash runway once inventory is stripped out. Operators and FP&A teams track the ratio by month so working-capital policy stays inside the board's liquidity band, not just inside a headline current-ratio covenant.
Lenders and sureties embed minimum defensive-interval tests in credit packs and need a deterministic check that matches the spreadsheet the borrower already signed, including the case of a zero daily-expense base that must fail rather than print Infinity. Educators and LMS platforms need an oracle for statement-analysis homework that asks students to compute the defensive interval ratio from liquid assets and average daily operating expenses—including the edge case of a zero daily-expense line students often mishandle by swapping the fraction. Failed validation is not billed.
Keep daily operating expenses positive, pin the rounded day count in tests, and you get reproducible coverage figures for spreadsheets, workflow tools, and edge workers without standing up a financial-ratio library of your own. Use this capability when you already have both inputs; if you want months of household essential expenses, that is an emergency-fund identity and does not belong in this defensive-interval definition.
What you can do with it
Treasury and 10-K liquidity screens
Convert period-end liquid assets and average daily operating expenses into days of defensive cover so companies rank by runway, not by raw cash balances.
Credit packs and covenant checks
Reproduce the borrower's minimum defensive-interval test with the same identity the loan model uses, including rejection when daily operating expenses are zero or negative.
Classroom statement-analysis drills
Mark homework that asks for the defensive interval ratio from liquid assets and daily operating expenses with a deterministic days-covered oracle.
FAQ
What counts as liquid assets for this ratio?
Cash and cash equivalents, marketable securities, and net receivables. Leave inventory and plant out; those are not defensive assets in this identity.
How do I calculate the defensive interval ratio?
Divide liquid assets by average daily operating expenses, both in the same currency and window. With 365000 of liquid assets and 1000 of daily expenses, the ratio is 365 days.
How do I work out average daily operating expenses?
Take operating expenses for the period, subtract non-cash charges such as depreciation and amortization, and divide by the days in the period, usually 365, or 360 in some bank models.
Why is inventory left out of the defensive interval?
Because turning stock into cash quickly usually means markdowns and disruption. The ratio counts only cash, marketable securities and net receivables, which convert without a fire sale.
How is it different from the current ratio or the quick ratio?
Those compare current assets with current liabilities at one moment. This one tells you how many days of operations the liquid stock can fund, and a comfortable current ratio can still hide a thin cash runway once inventory is removed.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/fin/defensive-interval-ratio \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"liquid_assets":365000,"average_daily_operating_expenses":1000}'const res = await fetch("https://api.kit.forhosting.com/fin/defensive-interval-ratio", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"liquid_assets": 365000,
"average_daily_operating_expenses": 1000
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/fin/defensive-interval-ratio",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"liquid_assets": 365000,
"average_daily_operating_expenses": 1000
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/fin/defensive-interval-ratio", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"liquid_assets":365000,"average_daily_operating_expenses":1000}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"liquid_assets":365000,"average_daily_operating_expenses":1000}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/fin/defensive-interval-ratio", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"liquid_assets": 365000,
"average_daily_operating_expenses": 1000
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "fin.defensive_interval_ratio",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
What the defensive interval ratio means and how the formula works
This endpoint does not fetch filings or ledger data; it only computes the days once you supply both numbers.
Input contract, rounding, validation, and worked examples
If you start from annual operating costs, subtract non-cash charges yourself and divide by 365 or your model's day count, then pass that daily figure. Example: liquid assets one hundred thousand and daily expenses three hundred sixty-five with decimals six yields about two hundred seventy-three point nine seven two six zero three days. POST a JSON body with two required finite numbers: liquid_assets and average_daily_operating_expenses, in the same currency. liquid_assets (aliases liquid_asset, liquid, defensive_assets, and liquid_resources) must be finite and greater than or equal to zero. average_daily_operating_expenses (aliases daily_operating_expenses, daily_expenses, average_daily_expenses, and average_daily_opex) must be a finite number strictly greater than zero because the defensive interval ratio divides liquid assets by daily operating expenses. An optional decimals integer from zero through twelve (default six) controls half-up rounding applied once to defensive_interval_ratio from the raw IEEE quotient; never re-inject a rounded day count into another formula step if you chain tools yourself. Missing fields, empty strings, non-finite values, a negative liquid-asset stock, and a zero or negative daily-expense base fail with invalid_input naming the issue, and those failures are not billed. Example: liquid assets three hundred sixty-five thousand and average daily operating expenses one thousand yields defensive_interval_ratio three hundred sixty-five. A firm with no liquid assets and a positive daily burn yields zero days of cover, which is a valid warning rather than a rejected input. Pair the response with your own industry notes; this endpoint measures the coverage days only and does not annualize, currency-convert, or decide which line items belong in the liquid stock unless you fold those classifications into the two inputs first.
Technical questions
How is the defensive interval ratio calculated?
defensive_interval_ratio = liquid_assets ÷ average_daily_operating_expenses. The API returns that quotient as days of operations the liquid stock can cover.
Why must average daily operating expenses be greater than zero?
The ratio divides by the daily burn. Zero or negative daily operating expenses make the identity undefined, so the task fails with invalid_input and is not billed.
Can liquid assets be zero?
Yes. A zero liquid stock on a positive daily burn yields defensive_interval_ratio 0 (zero days of cover). Negative liquid assets are rejected.
What does the defensive interval ratio calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.