GMAT score calculator
A practice pair of 49 Quantitative and 42 Verbal estimates a classic GMAT total of 730 on the 200 to 800 scale. Enter both section scores, 0 to 60, and get the total from the standard conversion table, in ten-point steps. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Quantitative
- 49
- Verbal
- 42
- Total
- 730
- Combined
- 91
- Scale min
- 200
- Scale max
- 800
The classic GMAT (10th Edition) reports Quantitative and Verbal section scores on a 0 to 60 scale and a Total Score from 200 to 800 in ten-point increments. Applicants, tutors, and admissions tools often have a practice-test pair of section scores and need the estimated total before an official report arrives. This GMAT score calculator accepts integer quantitative and verbal scores from 0 to 60, looks the pair up in the standard conversion table used by prep calculators, and returns the estimated total on the 200 to 800 scale. Integrated Reasoning and the Analytical Writing Assessment never enter the classic total.
What the standard GMAT conversion table actually maps
The official GMAT 10th Edition Total Score is not the sum of the two section scores and it is not a simple percentage of questions correct. Quantitative and Verbal are first scaled to the 0 to 60 range; most official reports fall between 6 and 51, but the published scale itself runs from 0 through 60. Those two scaled scores are then converted through a standard conversion table into a Total Score from 200 to 800 that steps by ten points.
Prep calculators encode that table as a function of the combined scaled score: a combined 12, the usual 6 plus 6 floor, maps to 200; a combined 102, the published 51 plus 51 pair, maps to 800; and every combined point in between is worth 600 divided by 90 total points before the result is snapped to the official ten-point grid. Combined scores at or below 12 stay at 200.
Combined scores at or above 102 stay at 800, so a theoretically possible 60 plus 60 pair still reports the published ceiling rather than a number no school would recognize. The table is why a 49 Quantitative and 42 Verbal pair is not 910 or 91 — it is an estimated 730. This capability stores that mapping as a deterministic lookup.
It does not use item-response theory, question-level data, or a live scoring service; it converts the two section scores you already have. Integrated Reasoning and the Analytical Writing Assessment are reported separately on the official 10th Edition exam and never change the 200 to 800 total, so they are not inputs here.
What to enter and what you get back
Each must be a whole number from 0 through 60 inclusive. On success the body echoes both section scores, returns combined as their sum, and returns total as the table lookup on the 200 to 800 scale. Example: quantitative 49 and verbal 42 yield combined 91 and total 730.
A 51 and 51 pair yields 800. A floor pair of 6 and 6 yields 200. Failed validation is not billed.
Where a GMAT score calculator earns its keep
MBA applicants use a GMAT score calculator after every practice test so they can compare a Quantitative and Verbal pair to school medians without waiting for an official report PDF. Tutors and bootcamps log weekly section scores and need a deterministic total that does not drift when two students with the same 47 and 40 sit down on different days. Admissions consulting CRMs store unofficial section scores from mocks and want a single estimated total for pipeline dashboards.
Exam-prep generators and learning-management plugins need an oracle that rejects a 61 the same way a real score report would refuse it, instead of silently clamping and marking a buggy form as correct. Pin the returned total in tests, keep both fields inside 0 to 60, and you get reproducible 200-to-800 estimates for homework, edge workers, and application trackers without standing up a scoring service of your own. Keep Focus Edition 60-to-90 scores out of this landing — that exam uses a different total scale and a different search intent.
What you can do with it
Practice-test score reports
Turn a mock Quant and Verbal pair into an estimated 200–800 total so applicants can compare the result to school medians the same day they finish the test.
Tutor and bootcamp tracking
Log weekly section scores and compute a stable total that does not change when two students post the same 47 and 40 on different days.
Admissions CRM unofficial totals
Store unofficial mock section scores and show one estimated total on pipeline dashboards without calling a live scoring service.
FAQ
How do I convert GMAT Quant and Verbal scores into a total?
Send integer quantitative and verbal scores from 0 to 60.
What happens if a section score is outside 0 to 60?
The published classic scale stops at 60, so a 61 is rejected instead of inventing a total above 800.
Do Integrated Reasoning or AWA change the total?
No. On the classic GMAT the 200–800 total comes only from Quantitative and Verbal. IR and the Analytical Writing Assessment are reported separately and are not inputs here.
Does this calculator work for the GMAT Focus Edition?
No. Focus Edition section scores run 60–90 and the total runs 205–805. This landing converts classic 0–60 section scores to the 200–800 total only.
What are the highest and lowest totals this calculator can give?
Totals run from 200 to 800 in ten-point steps. A combined score of 12 or less, such as 6 plus 6, stays at 200; a combined 102 or more, such as 51 plus 51, stays at 800, even a perfect 60 plus 60.
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/life/gmat-score \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"quantitative":49,"verbal":42}'const res = await fetch("https://api.kit.forhosting.com/life/gmat-score", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"quantitative": 49,
"verbal": 42
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/life/gmat-score",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"quantitative": 49,
"verbal": 42
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/life/gmat-score", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"quantitative":49,"verbal":42}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"quantitative":49,"verbal":42}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/life/gmat-score", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"quantitative": 49,
"verbal": 42
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "life.gmat_score",
"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 section score outside 0 to 60 fails with invalid_input instead of inventing a total.
Input contract, response shape, and error behaviour
POST a JSON body with two required integer fields: quantitative, the Quantitative section scaled score, and verbal, the Verbal section scaled score. JSON numbers and numeric strings are accepted; quantitative also accepts the aliases quant, q, quantitative_score, and quant_score, and verbal accepts v and verbal_score. Missing fields, empty strings, non-finite values, and non-integers fail with invalid_input and name the field so a form can highlight the broken control. A section score below 0 or above 60 also fails with invalid_input — the published scale stops at 60, and inventing an 810 would be a lie about what a score report can show. It also reports scale_min 200, scale_max 800, and increment 10 so clients can label the result without hard-coding the official grid, plus a short formula string that names the conversion table. This endpoint does not estimate percentiles, does not convert Focus Edition 60 to 90 section scores, and does not ingest unofficial raw question counts — feed it classic scaled section scores only.
Technical questions
What does the GMAT score calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.