ForHosting KIT · Home, food & hobbies

Tennis tiebreak score calculator

At 6–5 in a seven-point tiebreak, player A serves next, needs 1 point and player B needs 3. Enter both scores and who served first to keep the serve rotation and change of ends right. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Points a
6
Points b
5
You get
First server
A
Target
7
Output format
set
Score
6-5

A tennis set that reaches six games all is decided by a tiebreak, not another service game. Each player’s points tell you more than the scoreboard headline: whether the breaker is still live, who must hold serve next, and whether someone has already closed it out under the win-by-two rule. Coaches, umpires, streaming overlays, and league apps need that state from two integers without standing up a full match engine. This tennis tiebreak score calculator accepts each player’s points, who served the first point, and whether the breaker is a seven-point set tiebreak or a ten-point match tiebreak. It returns a deterministic board state: the printed score, whether the tiebreak is won, who serves the next point, whether the ends change, and how many points each player still needs.

How a tennis tiebreak is won, served, and finished

In a standard set tiebreak the first player to win at least seven points with a margin of two or more wins the set. Scores such as seven–five, seven–four, and seven–zero are finished; seven–six is not, because the leader does not yet lead by two, so play continues until someone pulls two points clear at eight–six, nine–seven, and so on. A match or super tiebreak uses the same win-by-two rule with a target of ten instead of seven, which is why this calculator accepts a target of seven or ten.

Serving is not one serve per point. The player who starts the breaker serves a single point; after that the players alternate two serves each. If player A starts, the serve order by next-point index is A, then B B, A A, B B, A A, and so on.

Players also change ends after every six points, so a live score whose total is a positive multiple of six (four–two, six–zero, six–six) means they walk before the next point. This capability reconstructs that entire state from the two point totals and who served first. It rejects impossible scores that would have stopped earlier: eight–five in a seven-point breaker is not a legal tennis score, because play would already have ended at seven–five.

It does not model the full match, game scoring of fifteen–thirty–forty, or challenge reviews. It models one breaker: whether it is still live, who must serve the next point, whether the ends change first, and whether someone has already won under the official first-to-N win-by-two rule.

Who relies on a tiebreak score calculator

Club umpires and league scorers use a tennis tiebreak score calculator so they never lose the serve rotation after a long six–six breaker or a ten-point match tiebreak that replaces a third set. Coaching tablets and practice apps log each point against a running pair of totals and need the same next-server and change-ends flags as the court, not a free-form note that drifts after a few changeovers.

Recreational players settling a club final can paste six–five and see immediately that the original server is back on the line, while a stats pipeline can reject an eight–five box score before it pollutes a results feed. Failed validation does not consume balance.

League and club scoring

Update a set or match tiebreak after each point and show who serves next, whether the ends change, and whether someone has already won.

Practice logs and coaching tablets

Record running point totals in a seven-point or ten-point breaker so solo drills and video reviews match official rotation and win-by-two rules.

How do I read the state of a tennis tiebreak from the two scores?

Optional target is 7 for a set tiebreak or 10 for a match tiebreak (default 7). The response says whether it is won, who serves next if it is not, and whether the players change ends.

When is a tennis tiebreak won?

When one player has at least the target (7 or 10) and leads by two or more. 7–5 is won; 7–6 is still live and continues until someone leads by two (8–6, 9–7, and so on).

Why is 8–5 rejected?

A seven-point tiebreak stops as soon as someone reaches seven with a two-point lead, so 8–5 could never be posted. The same rule rejects any winner total above max(target, loser + 2).

Who serves next in a tennis tiebreak?

The player who starts the tiebreak serves one point; after that the players alternate two serves each. If player A starts, the order is A, then B B, A A, B B, and so on.

When do players change ends during a tiebreak?

After every six points. When the total of a live score is a multiple of six, such as 4–2, 6–0 or 6–6, the players switch ends before the next point.

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.

POSThttps://api.kit.forhosting.com/hobby/sport-tennis-tiebreak

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.

curl -X POST https://api.kit.forhosting.com/hobby/sport-tennis-tiebreak \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"points_a":6,"points_b":5}'
{
  "points_a": 6,
  "points_b": 5
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "hobby.sport_tennis_tiebreak",
  "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.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Input contract, response shape, and validation

Optional target is seven for a set tiebreak or ten for a match tiebreak and defaults to seven. A pair that could not have been reached under sudden-death-at-target-plus-two is also rejected: the winner’s total must be exactly the maximum of the target and the loser’s total plus two. When it is finished those two keys are omitted and winner is present instead. POST a JSON body with two required integers. points_a is the points already won by player A: an integer from zero to ninety-nine inclusive. points_b is the same for player B. Optional first_server is a or b and names who delivered the opening point; it defaults to a. Field aliases are accepted for points_a (player_a, score_a, a_points), points_b (player_b, score_b, b_points), first_server (server, serve_first, first), and target (first_to, win_to). Values may arrive as JSON numbers or as whole decimal strings without leading zeros; missing fields, non-integers, out-of-range values, Infinity, and NaN fail with invalid_input naming the field and are not billed. On success the body echoes points_a, points_b, first_server, and target; adds format (set or match); score as a hyphenated string; total_points; won and status (in_progress or won); lead (a, b, or tied) and margin; points_to_win_a and points_to_win_b; a short formula; and a message. When the breaker is still live the body also includes next_server and change_ends. Example: points_a six and points_b five with defaults yields score six–five, won false, next_server a, change_ends false. points_a seven and points_b five yields won true and winner a. points_a eight and points_b five is invalid_input because play would have stopped at seven–five.

Where a tennis tiebreak score API earns its keep

Tournament overlays and streaming graphics can call a tiny parse endpoint between points without standing up a full match engine when all they need is who serves next and whether the set is over. Keep requests small, pin won, next_server, and change_ends in tests, and you get reproducible breaker math for scoreboards, LMS sports modules, and edge workers without hosting a tennis rules engine of your own.

Overlays and result feeds

Feed stream graphics or a results API a deterministic won flag, winner, and next server, and reject unreachable scores such as eight–five in a set tiebreak.

Who serves next in a tiebreak?

The first_server delivers one point, then the players alternate two serves each. At 6–5 with A starting, eleven points have been played and A serves the twelfth. next_server is omitted once the breaker is already won.

What does the tennis tiebreak 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.

Read the full KIT documentation →