Tonnage Calculator
The formula
What the tonnage tells you
The heavyweight version of volume load, reported in tonnes: how much metal the body actually moved in a session or a block.
Calculation: Tonnage = Σ volume; per kg = tonnage ÷ bodyweight. Enter your inputs and every substitution is shown below the result.
Reading the result
Tonnage is the dose meter — useful for week-to-week comparison, almost meaningless as an absolute target.
Rules of thumb: Advanced powerlifting session 8–15 t; CrossFit metcons well under 3 t
Limitations and best practice
More tonnage is never the goal; it is the accounting, and the best programs keep the books steady while intensity rises.
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
Tonnage vs volume load — difference?
Does it work for machines?
Source & methodology
Siff/Sheiko tonnage tracking tradition.
Tonnage explained: formula, worked example and honest limits
You are counting something that matters — this tool counts it exactly, including the edge cases calendars hide. Searchers land on a Tonnage page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
Most confusion about Tonnage comes from mixing up the input you control with the input you merely observe. The formula treats them identically, but your decisions should not: one deserves measurement, the other deserves a defensible estimate.
In Fitness & Sports the same quantity is often quoted under two or three different conventions. The formula printed above fixes one convention and applies it consistently, which is what makes results from this page comparable with each other.
Nothing below is stock text pasted around a number: the worked example computes session tonnage = 14.5 t from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Session volume load first, at ≈10.0 % 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.
Every input in Tonnage, and what it does to the answer
The engine implements a single stated model: Tonnage = Σ volume; per kg = tonnage ÷ bodyweight. 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.
Session volume load (kg) (example value 14,500) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Use the same conditions each time (same scale, same time of day) so that changes in the output reflect real change.
Bodyweight (kg) (example value 160) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Weigh rather than estimate where you can — this field usually enters the formula multiplicatively.
Weeks on this program (example value 3) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Use the value as of today, not as of the last time you looked — time fields drift silently.
Tonnage 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: Session volume load (kg), Bodyweight (kg), Weeks on this program. Run to the end, the session tonnage resolves to 14.5 t — This session moved 14.50 tonnes — 91 kg of load per kg of lifter; at 3 weeks that is 43.5 t cumulative, the stat meet-coaches use to spot over-dosing before the logbook admits it on the bands this tool uses.
- 14,500 kg ÷ 1000 = 14.50 tonnes
- ÷ 160 kg = 91 kg per kg bodyweight
- × 3 weeks = 43.5 t total
Tonnes per bodyweight kg — 91 kg/kg. Read next to the headline, this is the figure that shows the shape of the trade-off.
Weekly average load — 29,000 kg (2 sessions/wk). If your inputs change, this is usually the first companion figure to move.
Per-session band — standard hard day. If your inputs change, this is usually the first companion figure to move.
Deload trigger — tonnage >1.3 × baseline for 2 weeks. If your inputs change, this is usually the first companion figure to move.
Re-running with your own figures is instant; re-running by hand once is the best way to know the tool is telling you the truth.
The Tonnage corridor: your result across a realistic band
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Session volume load setting | Session tonnage |
|---|---|
| 80 % of the example value | 11.6 t |
| 90 % of the example value | 13.1 t |
| example inputs | 14.5 t |
| 110 % of the example value | 16.0 t |
| 120 % of the example value | 17.4 t |
That spread — 11.6 t at the low end, 17.4 t at the high — is what a careful read of Tonnage looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Session volume load alone; the substitution steps will follow your figures exactly.
Sensitivity: which inputs change Tonnage the most
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the session tonnage recomputed, so the ranking below is measured rather than asserted. It is the fastest honest answer to “what matters most in Tonnage?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- Session volume load +10 % → Tonnage = 16.0 t · −10 % → 13.1 t (the session tonnage shifts ≈10.0 %)
Session volume load is the dominant lever here: ten percent either way moves the result by about 10.0 %, from 13.1 t to 16.0 t. That is where a careless figure does the most damage, so check it against a source. The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
What a Tonnage of 14.5 t means in practice
Nobody acts on a bare figure — they act on a figure with a comparison attached. The default case lands in the “This session moved 14.50 tonnes — 91 kg of load per kg of lifter; at 3 weeks that is 43.5 t cumulative, the stat meet-coaches use to spot over-dosing before the logbook admits it” band, and bands are deliberately wide because real situations overlap. The sensitivity list shows how far a modest input error moves you along that ladder: for Session volume load, ±10 % covers 13.1 t to 16.0 t. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
In Fitness & Sports, Tonnage is one instrument in an orchestra: on its own it is a number, next to Tonnes per bodyweight kg and Weekly average load it becomes a diagnosis. The tools linked above exist so the headline never has to carry that weight alone.
Why Tonnage results go wrong — and how to prevent it
More tonnage is never the goal; it is the accounting, and the best programs keep the books steady while intensity rises. 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.
Copying a single headline number without checking the companion outputs. The tool reports Tonnes per bodyweight kg, Weekly average load and Per-session band alongside the main result precisely because Tonnage in isolation misleads — the secondary columns are where outliers and trade-offs show up.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Session volume load first, everything else second.
Another is comparing across contexts: a Tonnage computed with one set of conventions should never be lined up against a figure computed with another. Check the inputs behind both before ranking them.
Tonnage verification checklist
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Note the date and the inputs beside the number so the figure can be audited later.
- Put Session volume load under a magnifier; the sensitivity table above is the reason why.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Confirm the example values are plausible for your own situation before replacing them.
- Confirm the answer against one independent method or published benchmark for Tonnage.
Step by step: getting a trustworthy Tonnage out of this tool
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — one document, one pass. Open the statement, label or record that holds session volume load (kg), bodyweight (kg), weeks on this program and transcribe straight into the form. Transcription from a single source removes the mismatch errors that appear when figures are assembled from three different places. If a result feels obviously right, that is the moment to check the inputs hardest.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the Session tonnage (14.5 t for the example values), and note the verdict band. When two sources disagree, it is almost never the arithmetic that differs.
Step 3 — isolate your variables. Change one field, observe, revert. The live sensitivity list does the ranking for the default inputs; verify it against your own, because dominance shifts when the starting point shifts. Write the assumptions in the same file as the result, and future arguments take minutes instead of meetings.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Step 5 — write the one-line memo. “Session tonnage = 14.5 t on this date, from these inputs.” That line is the entire deliverable; everything else on this page is how you earned the right to write it. When two sources disagree, it is almost never the arithmetic that differs.
The real-world conversations Tonnage settles
Fitness & Sports arguments end at arithmetic or they do not end. Tonnage is the arithmetic: 14.5 t on the example inputs, reproducible by anyone who types the same numbers. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Used properly this is a five-minute filter that saves weeks. Compute Tonnage, reject what fails, and only then bring in the expensive analysis for the survivors. The input you reach for first is usually the one you measured longest ago.
Nothing here is stored or transmitted, so the habit of checking is free: open the page, re-enter current figures, compare with the number you saved last time. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Quick answers: what searchers ask about Tonnage
What affects Tonnage the most?
The short answer: Session volume load. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the session tonnage recalculated — Session volume load moved it furthest, by roughly 10.0 % (13.1 t to 16.0 t).
What is a typical Tonnage?
With the example inputs on this page the result is 14.5 t, labelled “This session moved 14.50 tonnes — 91 kg of load per kg of lifter; at 3 weeks that is 43.5 t cumulative, the stat meet-coaches use to spot over-dosing before the logbook admits it”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate Tonnage by hand?
Three steps: write the formula (Tonnage = Σ volume; per kg = tonnage ÷ bodyweight), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Tonnage than any number of calculator runs.
What happens to Tonnage if session volume load changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 13.1 t to 16.0 t across the ten-percent probe, i.e. ≈10.0 % sensitivity on the session tonnage.
Is the Tonnage result of 14.5 t good or bad?
The tool answers “what”, not “whether”: 14.5 t carries the verdict “This session moved 14.50 tonnes — 91 kg of load per kg of lifter; at 3 weeks that is 43.5 t cumulative, the stat meet-coaches use to spot over-dosing before the logbook admits it” for the default case, which is a starting interpretation rather than a verdict on your situation. Re-run with your own figures and compare the bands.
Can Tonnage be negative or empty?
Yes, and that is informative rather than broken: a negative Tonnage usually means the inputs encode an outflow or a shortfall, and the verdict band above labels exactly that situation instead of hiding it.
How do I calculate Tonnage manually?
Write down the inputs, then follow the printed steps in order — Tonnage = Σ volume; per kg = tonnage ÷ bodyweight. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
Tonnage vs volume load — difference?
Units: tonnage is volume load expressed in tonnes for the whole session or block.
Does it work for machines?
Yes, if you record the stack × reps honestly.
Does this Tonnage tool store my numbers?
No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Fitness & Sports figures and the reason you can re-run this page as often as you like.
Key terms on this page
- Tonnes per bodyweight kg
- 91 kg/kg in the default Tonnage calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Weekly average load
- 29,000 kg (2 sessions/wk) on the example inputs — a companion figure printed beside the headline of Tonnage so that no result is read in isolation.
- Per-session band
- standard hard day in the default Tonnage calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Session tonnage
- The primary output of this tool: 14.5 t for the default inputs, computed exactly from Tonnage = Σ volume; per kg = tonnage ÷ bodyweight.
- Worked example
- Every substitution in order, from the example inputs to 14.5 t — the audit trail for the headline figure.
- Verdict band
- A named zone on the range of plausible results; the example inputs land in “This session moved 14.50 tonnes — 91 kg of load per kg of lifter; at 3 weeks that is 43.5 t cumulative, the stat meet-coaches use to spot over-dosing before the logbook admits it”, and your inputs may not.
- Sensitivity (±10 %)
- How far the Tonnage moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Where the Tonnage model comes from
The model is published arithmetic implemented exactly as written: Tonnage = Σ volume; per kg = tonnage ÷ bodyweight. Source of record: Siff/Sheiko tonnage tracking tradition. Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
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 Tonnage into a decision
Mark the computed date or span in your calendar with its assumptions attached; plans drift when the inputs do.
The audience here is people planning around a point or span in time. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.