UPS runtime calculator
Estimate UPS runtime from entered battery energy, load, efficiency and usable-fraction assumptions for Australian backup power records.
Runtime = battery energy Wh x usable fraction x efficiency / load W- Battery energy is entered directly in Wh.
- Usable fraction and efficiency are entered percentages.
- Runtime divides usable energy by the entered steady load.
| Variable | Meaning | Unit | Use |
|---|---|---|---|
| Ebat | Battery energy | Wh | Entered UPS battery energy basis. |
| Fusable | Usable fraction | ratio | Entered usable share of battery energy. |
| Eta | Efficiency | ratio | Entered UPS or planning efficiency. |
| Eusable | Usable energy | Wh | Battery energy multiplied by usable fraction and efficiency. |
| Pload | Load | W | Entered load supported by the UPS. |
| t | Runtime | h | Usable energy divided by load watts. |
More
UPS runtime calculator technical guide
Estimate UPS runtime from entered battery energy, load, efficiency and usable-fraction assumptions for Australian backup power records.
Use this calculator when the work question is runtime from an entered UPS battery-energy basis. It is useful for small backup records, communications loads, critical-load notes and early operating comparisons where the user has a Wh value and a load value to record.
UPS runtime is product-dependent, so the calculator is intentionally framed as a worksheet. It does not replace UPS manufacturer runtime curves, battery test data, temperature correction, age allowance or site-specific operating requirements. Its value is that it makes battery energy, load, efficiency and usable fraction visible in one record.
UPS Runtime Use Cases
| Work setting | Real question | Useful action from this page |
|---|---|---|
| Small UPS backup | How long may the entered Wh value support the load? | Enter battery energy, load, efficiency and usable fraction. |
| Communications load | Does a modest load have enough runtime for a backup note? | Use runtime minutes and usable energy together. |
| Critical-load record | Which assumptions should be visible before product data is checked? | Export the Wh, load and efficiency basis. |
| Battery condition review | Is the usable fraction doing too much work? | Treat high usable fraction as a review prompt. |
| Target-runtime planning | What if the required runtime is known first? | Move to the UPS battery sizing calculator. |
A strong UPS runtime record names the load and UPS basis. A runtime value without battery energy, load and usable fraction is difficult to review later, especially when batteries age or the supported load changes.
UPS Runtime Boundary
| Item | Included in the arithmetic | Boundary to keep separate |
|---|---|---|
| Battery energy | Entered Wh value. | Product battery configuration, age and tested capacity remain external. |
| Load | Entered steady watts. | Load profile, power factor, inrush and cycling behaviour are not modelled. |
| Efficiency | Entered percentage. | UPS operating mode and product curve can change real losses. |
| Usable fraction | Entered percentage. | Battery chemistry, warranty, BMS and end-voltage limits can override it. |
| Australian context | Backup-power context is noted. | Installation, product and local requirements remain separate checks. |
This boundary keeps the worksheet from becoming a product selector. A runtime result can be useful, but UPS decisions should still use product data and a record of the actual loads being supported.
Input Checklist
| Value | Where it normally comes from | Why it matters |
|---|---|---|
| Battery energy | UPS product record, battery schedule or project assumption | Sets the energy pool before losses. |
| Supported load | Critical-load list, measured load or equipment schedule | Runtime changes directly with load. |
| Efficiency | UPS product data or documented planning basis | Keeps conversion losses visible. |
| Usable fraction | Product data, battery condition note or conservative assumption | Controls how much stored energy is assumed available. |
| Runtime reference | UPS, load group or backup scenario label | Keeps the estimate traceable. |
If the supported load is variable, make separate records for the scenarios that matter. A single average can hide the load that controls runtime during a real outage.
Review Workflow
- Name the UPS, critical load or backup scenario.
- Enter the battery energy basis in Wh.
- Enter the steady load in watts.
- Enter the UPS or planning efficiency.
- Enter the usable fraction for the record.
- Read usable energy before relying on runtime.
- If runtime is short, check the load and battery-energy basis.
- If usable fraction is high, check UPS product data and battery condition.
- Keep runtime curves, battery age, temperature and site requirements outside the arithmetic result.
- Use battery sizing when the target runtime is the starting question.
The workflow lets the record explain itself. It does not decide whether the UPS product is suitable for the site or whether battery replacement is needed.
Worked Records
| Situation | Inputs | Result pattern | Interpretation |
|---|---|---|---|
| Small UPS backup | 3000 Wh, 900 W, 90% efficiency, 80% usable | 2160 Wh usable and 2.4 h runtime | Useful worksheet value before product curve review. |
| Communications backup | 1200 Wh, 300 W, 92% efficiency, 75% usable | Longer small-load runtime | Useful as a backup note while battery condition remains external. |
| High usable-fraction review | 1000 Wh, 6000 W, 90% efficiency, 95% usable | Short-runtime review | Check product data, load basis and usable-fraction support. |
Australian Context
UPS records in Australia often sit beside backup generator, battery, inverter, power-quality and critical-load notes for 230/400 V, 50 Hz installations. This page only owns the energy arithmetic. Installation requirements, product instructions, battery replacement policy, bypass arrangements, ventilation and authority expectations remain outside the calculator.
When the result feeds a project decision, check UPS manufacturer data, battery manufacturer data, site conditions and project requirements. Keep this page as a clear entered-data record.
Stop Points
- Battery energy basis is unknown or copied from another UPS model.
- Supported load varies materially across the backup period.
- Usable fraction is high without product or battery-condition support.
- Runtime curves, battery age or temperature data are needed.
- The runtime result is being treated as product selection or site approval.
Small UPS backup record
A UPS battery-energy note uses 3000 Wh, a 900 W load, 90% efficiency and 80% usable fraction.
- Reference
- UPS-RUN-1
- Battery energy
- 3000 Wh
- Load
- 900 W
- Efficiency
- 90%
- Usable fraction
- 80%
- Usable energy2160 Wh
- Runtime2.4 h
- Runtime minutes144 min
2160 Wh usable energy from the entered basis.
The result is a runtime worksheet value for a backup record, not a product selection.
- Battery energy is entered by the user.
- Efficiency is an entered planning basis.
- Product curves and battery condition remain external.
Communications load note
A smaller communications load is checked against a modest UPS energy record.
- Reference
- UPS-RUN-COMMS
- Battery energy
- 1200 Wh
- Load
- 300 W
- Efficiency
- 92%
- Usable fraction
- 75%
- Usable energy828 Wh
- Runtime2.76 h
- Runtime minutes166 min
828 Wh usable energy from the entered basis.
The usable-energy and runtime values can sit beside a comms backup note.
- Load is treated as steady.
- Usable fraction is deliberately visible.
- Battery age and temperature are outside the arithmetic.
High usable-fraction review
A high usable fraction shows when the UPS record needs closer review before reuse.
- Reference
- UPS-RUN-REVIEW
- Battery energy
- 1000 Wh
- Load
- 6000 W
- Efficiency
- 90%
- Usable fraction
- 95%
- Usable energy855 Wh
- Runtime0.14 h
- Runtime minutes9 min
855 Wh usable energy from the entered basis.
The short duration and high usable fraction should be checked before the record is used.
- The high load is intentional.
- The usable fraction needs product support.
- Battery and UPS product data can override the worksheet.