Rounds per minute calculator
Turn a cadence measured per second or per hour into rounds per minute: 10 rounds per second is 600 RPM and 36,000 per hour, all three shown together so range cards and manuals match. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Interest rate
- 10
- Per
- Second
- Rounds per minute
- 600
- Rounds per second
- 10
- Rounds per hour
- 36,000
A rounds per minute calculator converts a firing cadence given per second or per hour into the cyclic rate people actually quote: rounds per minute, often written RPM on range cards, manuals, and procurement sheets. Enter a finite non-negative rate and say whether that count is per second or per hour; the tool multiplies by sixty or divides by sixty and returns rounds per minute plus the equivalent per-second and per-hour figures. Zero is a valid quiet baseline. There is no network call, no wall clock, and no randomness.
How firing cadence becomes rounds per minute
A minute is sixty seconds and an hour is sixty minutes, so converting a cyclic fire rate is a one-step scale between those three windows. When the input is rounds per second, rounds per minute equals the given rate times sixty: ten rounds per second is six hundred rounds per minute, because each of those ten events repeats sixty times inside a civil minute.
When the input is rounds per hour, rounds per minute equals the given rate divided by sixty: three thousand six hundred rounds per hour is sixty rounds per minute. The same identities run in reverse so the response can also echo rounds per second and rounds per hour without a second request. Zero is a legal cadence and yields zero in every window.
The implementation never consults Date, never calls a network service, and never uses randomness, so the same pair of rate and time base always produces the same rounded numbers and formula.
Where a rounds-per-minute converter earns its keep
Armourers, range officers, and technical writers open a rounds per minute calculator when a source lists cyclic rate in rounds per second or rounds per hour and a card, table, or specification sheet must show RPM. Historical notes often quote a weapon or marker in rounds per second from a short burst stopwatch; multiplying by sixty is the whole conversion, but doing it by hand next to mixed units is how transcription errors sneak into manuals.
Procurement and comparison pages need the same number when one vendor publishes per-second cyclic rate and another publishes per-hour throughput of a dispenser, feeder, or marker. Prefer it when you already know the cadence and only need RPM.
What you can do with it
Range cards and cyclic-rate tables
Armourers convert a stopwatch cadence in rounds per second into the rounds-per-minute figure that range cards and manuals already use.
Training logs and simulator exports
Simulators store burst cadence per second or per hour; a single call fills a consistent RPM column for briefs, CSVs, and dashboards.
Vendor sheets with mixed time bases
Procurement teams compare a per-second cyclic rate from one sheet with a per-hour throughput from another by converting both to RPM.
FAQ
How do you convert rounds per second to rounds per minute?
Multiply the per-second rate by sixty. Ten rounds per second is six hundred rounds per minute. The response also echoes the equivalent per-hour figure.
How do you convert rounds per hour to rounds per minute?
Divide the per-hour rate by sixty. Three thousand six hundred rounds per hour is sixty rounds per minute.
What happens if the input rate is negative?
A firing cadence on this landing is not a signed ledger, so a negative rate is rejected and is not billed.
Is a rate of zero allowed?
Yes. Zero rounds per second or per hour yields zero rounds per minute, which is a useful quiet baseline in logs and tests.
How many rounds per hour is 10 rounds per second?
It is 36,000 rounds per hour. Ten per second gives 600 per minute, and that figure times 60 gives the hourly value; the calculator returns all three from a single entry.
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/biz/rounds-per-minute \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"rate":10,"per":"second"}'const res = await fetch("https://api.kit.forhosting.com/biz/rounds-per-minute", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"rate": 10,
"per": "second"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/biz/rounds-per-minute",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"rate": 10,
"per": "second"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/biz/rounds-per-minute", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"rate":10,"per":"second"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"rate":10,"per":"second"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/biz/rounds-per-minute", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"rate": 10,
"per": "second"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "biz.rounds_per_minute",
"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_abs | 1000000000 |
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
Negative rates fail with invalid_input and are not billed. Successful API requests cost $0.002.
How firing cadence becomes rounds per minute
A negative rate is rejected because a firing cadence on this landing is not a signed ledger; the task fails with invalid_input naming the field and is not billed. That determinism is what lets a range card, a documentation generator, and an API job print the same RPM for the same input.
Input contract, response fields, and validation errors
Ten rounds per second maps to six hundred rounds per minute. Three thousand six hundred rounds per hour maps to sixty rounds per minute. Failed validation is never charged. POST a JSON body with two required fields. rate is a finite non-negative number of rounds in the chosen time base; aliases cadence, value, firing_rate, rounds, and cyclic_rate are accepted so a form, a query string, or a spreadsheet column can reuse the same contract. per is the time base of that count and must be second or hour; aliases unit, time_base, period, cadence_unit, and from are accepted, and the solver also recognizes common tokens such as s, rps, hour, and rph before normalizing to the canonical enum. The rate may arrive as a JSON number or as a decimal numeric string, including scientific notation; Infinity, NaN, empty strings, and non-numeric tokens fail with a message that names the field. Values above one billion in absolute magnitude are rejected so intermediate products stay finite on the Worker and in the browser. On success the body echoes the rounded rate and the canonical per token, then returns rounds_per_minute as the primary cyclic rate, plus rounds_per_second, rounds_per_hour, and a formula string restating the two identities. Successful API calls use the published $0.002 base price.
Where a rounds-per-minute converter earns its keep
Training simulators and logging apps store raw cadence in whichever window their sensor used, then call this endpoint once so dashboards, CSV exports, and printed briefs share a single rounds_per_minute column. Content sites that rank for rounds per minute calculator benefit from a live tool that needs no signup for one-off checks while automation clients pay the published $0.002 base price per successful call with no model tokens and no outbound network. This landing is a unit converter, not a ballistic solver: it does not estimate recoil, muzzle energy, or legal classification. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when you deliberately send a negative rate to test client validation.
Technical questions
What does the rounds per minute calculator cost?
The browser tool is free. API requests use prepaid balance at $0.002 per successful call; invalid input is not billed.