Burpee calorie calculator
50 burpees in 5 minutes at 70 kg burn about 49 kcal: your pace of 10 per minute sets the intensity at 8 METs, and the standard oxygen-cost formula does the rest, step by step. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Weight
- 70
- Repetitions
- 50
- Duration
- 5
- Calories kcal
- 49 kcal
- Calories burned
- 49
- Weight (kg)
- 70
- Duration minutes
- 5
A burpee calorie calculator turns three numbers you already have after a session into an estimated energy cost in kilocalories: body weight in kilograms, how many burpees you completed, and how long the bout lasted in minutes. Cadence, which is repetitions divided by minutes, selects a metabolic equivalent anchored at eight METs when you average ten burpees per minute, matching vigorous calisthenics in the Compendium of Physical Activities. The ACSM oxygen-cost identity then multiplies MET, 3.5 millilitres of oxygen per kilogram per minute, body mass, and duration, dividing by 200 to yield kilocalories.
What burpee calories mean and how cadence sets MET
Calories burned doing burpees are an estimate of the extra energy your body spends completing a squat-to-plank-to-jump cycle, not a laboratory calorimetry measurement and not a full daily energy expenditure figure. Exercise physiologists express that cost through metabolic equivalents. One MET is the oxygen cost of quiet sitting, about 3.5 millilitres of oxygen per kilogram of body mass per minute.
Vigorous calisthenics such as burpees, jumping jacks, and push-up circuits sit near eight METs in the Compendium of Physical Activities when the work rate is about ten repetitions per minute. Faster cadences raise intensity toward high-interval bands; slower cadences drop toward moderate calisthenics. This calculator interpolates MET as six plus two-tenths times cadence in burpees per minute, then clamps the result between five and fourteen so a crawl or an all-out sprint cannot invent an unbounded cost.
Kilocalories follow the ACSM oxygen identity: MET times 3.5 times body weight in kilograms times duration in minutes, divided by two hundred. That is the same as converting oxygen uptake to litres and multiplying by about five kilocalories per litre. Treat the figure as a transparent training-log number you can recompute by hand, not as medical advice or a promise of fat loss, which also depends on diet, recovery, and total daily expenditure.
Practical tips, limits, and related searches
Count only completed burpees with a visible hip extension and a jump or stand at the top; half-reps inflate cadence and would overstate MET if you rounded them up. Use the clock for the working set, not the whole class including rest, unless you truly want a lower average cadence. Stay inside the published limits: body mass from one to five hundred kilograms, repetitions from one to one hundred thousand, duration from a hundredth of a minute up to one day.
Extreme cadences clamp MET at five or fourteen rather than extrapolating without bound. This page targets people searching for a burpee calorie calculator, calories burned doing burpees, or kcal from burpee reps and duration; it is not a running, cycling, swimming, or walking estimator, not a heart-rate calorie model, and not a TDEE planner. Prefer this capability when you already know body weight, a whole-number rep count, and session minutes and only need a deterministic kilocalorie figure.
Round-trip checks are easy: fifty burpees at seventy kilograms in five minutes should return forty-nine kilocalories from MET eight, and doubling duration at the same reps should lower cadence, lower MET, and change the total in the documented proportion.
What you can do with it
HIIT and CrossFit session logs
Athletes enter body weight, completed burpees, and working-set minutes to fill a consistent kcal column in a WOD or interval diary.
Classroom exercise-science drills
Teachers generate answer keys that multiply cadence-based MET by kilograms and minutes without spreadsheet drift or guessed per-rep rules of thumb.
App and timer kcal columns
Workout timers store weight and a whole-number rep count, then call this tool once to publish kcal, MET, and cadence next to the clock.
FAQ
How are burpee calories calculated?
Cadence is repetitions divided by duration in minutes. MET equals clamp(6 + 0.2 × cadence, 5, 14), then kilocalories equal MET × 3.5 × body weight in kg × duration in minutes / 200 (ACSM oxygen-cost identity).
Why does how fast I do the burpees change the result?
Faster cadence raises MET toward vigorous and HIIT bands; slower cadence lowers MET toward moderate calisthenics. The same rep count over a longer clock therefore uses a lower MET for more minutes.
What happens if repetitions is zero, negative, or a decimal?
Repetitions must be a positive integer (1, 2, 3, …). Fractional or empty rep counts are rejected rather than rounded.
Is duration required in minutes?
Yes. Duration is session length in minutes. Convert seconds by dividing by sixty before you call. Weight is kilograms.
Is the burpee calorie calculator free?
The browser tool is free and runs locally.
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/sports/burpee-calorie \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"weight":70,"repetitions":50,"duration":5}'const res = await fetch("https://api.kit.forhosting.com/sports/burpee-calorie", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"weight": 70,
"repetitions": 50,
"duration": 5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/sports/burpee-calorie",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"weight": 70,
"repetitions": 50,
"duration": 5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/sports/burpee-calorie", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"weight":70,"repetitions":50,"duration":5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"weight":70,"repetitions":50,"duration":5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/sports/burpee-calorie", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"weight": 70,
"repetitions": 50,
"duration": 5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "sports.burpee_calorie",
"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.
Limits
max_weight_kg | 500 |
max_repetitions | 100000 |
max_duration_min | 1440 |
min_weight_kg | 1 |
min_duration_min | 0.01 |
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
Repetitions that are not a positive integer fail with invalid_input so a fractional, zero, or missing rep count never looks like a completed workout.
What burpee calories mean and how cadence sets MET
The estimate is deterministic: identical weight, repetitions, and duration always yield the same rounded JSON, with no network, no random seeds, and no wall-clock dependence.
How to call the API and what comes back
If you already know a generic MET and only need MET times kilograms times hours, that is a different search; this landing is specifically calories burned doing burpees from weight, reps, and time. Send a JSON body with three required fields. The field weight is body mass in kilograms, a finite positive number between one and five hundred, with aliases body_weight, weight_kg, kg, and mass. The field repetitions is the count of completed burpees and must be a positive integer from one through one hundred thousand; aliases are reps, n, count, and burpees. Zero, negatives, decimals, empty strings, and non-numeric values fail with invalid_input and are never charged. The field duration is session length in minutes, a finite positive number between 0.01 and 1440, with aliases duration_min, duration_minutes, minutes, time, and mins. On success the response echoes cleaned weight_kg, repetitions, duration_minutes, and duration_hours; publishes cadence_per_min and the interpolated met; returns calories_kcal and calories_burned as the same total, unit set to kcal, plus kcal_per_hour and kcal_per_rep; and includes formula, method burpee_met_cadence_acsm, a short message, and an ordered steps array showing the cadence, MET clamp, and ACSM substitution. A classic check is seventy kilograms, fifty burpees, and five minutes: cadence ten, MET eight, forty-nine kilocalories. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Practical tips, limits, and related searches
Prefer a recent weigh-in in kilograms; this contract takes kilograms so API clients do not need a separate unit library. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when you deliberately send a decimal rep count to test client validation. API pricing remains $0.002 per successful request with unit item.