Wastewater BOD removal efficiency calculator
Influent BOD of 250 mg/L and effluent of 25 mg/L mean 90 % removal: the calculator compares what enters and leaves the plant and shows the concentration removed and the share that remains. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Influent
- 250
- Effluent
- 25
- Removed
- 225 %
- Efficiency percent
- 90
- Remaining percent
- 10
Biochemical oxygen demand, or BOD, is the mass of dissolved oxygen that microorganisms consume while oxidizing biodegradable organic matter in a water sample, most often reported as five-day BOD5 at twenty degrees Celsius. Wastewater treatment plants, industrial pretreatment programs, and environmental consultants measure how well a process strips that oxygen demand by comparing the BOD that arrives in the influent with the BOD that leaves in the treated effluent. This wastewater BOD removal efficiency calculator applies the plant-performance identity used in textbooks and discharge reports: efficiency percent equals influent minus effluent, divided by influent, times one hundred. Enter two finite concentrations in the same unit and the task returns the removal percentage together with the concentration removed.
What BOD removal efficiency means at a wastewater plant
Biochemical oxygen demand is a surrogate for biodegradable organic strength. A sample is incubated, typically for five days in the dark at twenty degrees Celsius, and the oxygen consumed by the mixed culture is reported as milligrams per litre. That number is not a chemical inventory of every organic compound; it is the oxygen that receiving waters would have to supply if the same load were discharged untreated.
A municipal plant therefore tracks two BOD numbers on every reporting day: the influent concentration at the headworks and the effluent concentration at the outfall or the last process unit. Removal efficiency converts those two concentrations into a single percentage that operators, regulators, and design engineers already share. The identity is η equals influent minus effluent, all divided by influent, times one hundred.
If the plant receives two hundred fifty milligrams per litre and discharges twenty-five, ninety percent of the incoming oxygen demand has been removed and ten percent remains. Primary clarification alone often lands near thirty to forty percent BOD removal because settleable solids carry a large share of the load. Conventional activated sludge, trickling filters, and oxidation ditches commonly reach eighty-five to ninety-five percent on municipal wastewater when aeration, solids retention time, and temperature are in range.
The calculator does not replace a process model: it does not estimate hydraulic retention time, mixed-liquor suspended solids, or the first-order rate constant k. It answers the reporting question that appears on monthly operating reports and student lab sheets: given these two BOD concentrations, what percent was removed.
Plant logs, lab reports, and when this percentage is enough
Operators use the percentage as a daily health check against the plant’s own baseline, not as a substitute for dissolved-oxygen profiles or sludge-volume-index readings. Consulting engineers fold the same ratio into performance guarantees and bid evaluations: a secondary process specified at ninety percent BOD removal is checked by this identity, not by a kinetic simulation, once the measured pair is in hand.
Teaching labs can fix influent at two hundred milligrams per litre and walk effluent from one hundred down to ten so students see efficiency climb from fifty percent to ninety-five percent without opening a spreadsheet. Limits stay honest: this tool does not convert BOD to COD or TOC, does not apply a temperature correction, does not compute population equivalent, and does not decide whether a discharge permit was met—permits often state an absolute effluent limit in milligrams per litre as well as, or instead of, a percent removal.
Search intent for this landing includes wastewater BOD removal efficiency calculator, influent and effluent BOD percent removal, and wastewater treatment plant BOD efficiency.
What you can do with it
Daily plant operating reports
Convert paired influent and effluent BOD5 results into a percent removal for the monthly operating report and the operator’s shift log.
Design and performance guarantees
Check a secondary-treatment guarantee (for example 90% BOD removal) against measured headworks and outfall concentrations without opening a process model.
Teaching the plant-performance identity
Let students enter textbook pairs such as 250 and 25 mg/L and see that η = (Cin − Cout) / Cin × 100 is exactly 90%.
FAQ
How do I calculate wastewater BOD removal efficiency?
Send finite influent and effluent BOD concentrations in the same unit.
What units should I use for influent and effluent?
Any consistent mass-per-volume unit. Plant data are usually five-day BOD5 in mg/L. The ratio is dimensionless, so mixing units (mg/L with g/m³ that are not converted) will silently mis-report the percent.
What does 90% BOD removal mean?
That the plant took out nine tenths of the incoming oxygen demand. With 250 mg/L in the influent and 25 mg/L in the effluent, 225 mg/L were removed and 10 % remains in the treated water.
What if effluent BOD is higher than influent BOD?
The efficiency comes out negative, which shows that the process added oxygen demand between the inlet and the outlet instead of removing it. The calculator reports that value as it is.
What is BOD5?
Five-day biochemical oxygen demand: the oxygen that microorganisms consume while breaking down biodegradable organic matter in a sample incubated in the dark for five days at twenty degrees Celsius, reported in milligrams per litre.
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/bio/wastewater \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"influent":250,"effluent":25}'const res = await fetch("https://api.kit.forhosting.com/bio/wastewater", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"influent": 250,
"effluent": 25
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/bio/wastewater",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"influent": 250,
"effluent": 25
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/bio/wastewater", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"influent":250,"effluent":25}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"influent":250,"effluent":25}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/bio/wastewater", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"influent": 250,
"effluent": 25
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "bio.wastewater",
"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
A zero or negative influent concentration makes the ratio undefined and fails with invalid_input.
Input contract, formula, and how errors are raised
Typical plant data are five-day BOD5 in milligrams per litre, but any consistent mass-per-volume unit works because the ratio is dimensionless. A zero or negative influent is rejected because the denominator of the plant ratio would be zero or would invert the meaning of a concentration; the message states that removal efficiency is undefined when the influent concentration is zero or negative. A negative effluent is rejected because a concentration cannot be below zero. Failed validation is not billed. POST a JSON body with two required finite numbers in the same unit: influent, the incoming BOD concentration, and effluent, the outgoing BOD concentration. Aliases accepted for influent include influent_bod, bod_in, c_in, cin, bod_influent, and influent_concentration. Aliases for effluent include effluent_bod, bod_out, c_out, cout, bod_effluent, and effluent_concentration. On success the response echoes influent and effluent with stable twelve-decimal rounding, plus removed as influent minus effluent, efficiency_percent as the primary result, remaining_percent as one hundred minus that efficiency, unit as the percent sign, formula restating η = (influent − effluent) / influent × 100, and a short English message. Missing fields, empty strings, booleans, NaN, and Infinity fail with invalid_input naming the field. An effluent larger than the influent is allowed and returns a negative efficiency_percent: that is the honest signal that the process added oxygen demand, for example by recycling a sidestream or losing solids over the weirs. Successful work is priced at a flat $0.002 with unit item.
Plant logs, lab reports, and when this percentage is enough
Typical workflow: collect paired composite samples of influent and effluent, run the BOD5 incubation, and enter the two reported concentrations here to log efficiency_percent next to the date and the train identifier. Automation scripts can store one influent and one effluent per outfall and call the API after each laboratory information-management-system import. Round-trip checks are straightforward: recompute influent minus effluent over influent times one hundred and confirm equality with efficiency_percent within published rounding, then confirm that a zero influent flips the response from success to invalid_input.
Technical questions
Why was my request rejected?
Missing fields, non-finite values, a zero or negative influent, or a negative effluent fail with invalid_input and are not billed. Zero influent makes the removal ratio undefined.
What if effluent BOD is higher than influent BOD?
The calculator returns a negative efficiency_percent. That is a valid plant signal (solids washout, sidestream return, or a sampling error), not an input error.
What does the wastewater BOD calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.