How to Keep Score in Darts: A 501 Walkthrough

How to keep score in darts: read each landing

The large numbered segments score their number. The narrow outer ring doubles it, and the narrow inner ring trebles it. A single twenty is 20, double twenty is 40, and treble twenty is 60. The outer bull scores 25 and the inner bull scores 50.

A standard visit allows up to three darts. Add the values of the darts that count, then subtract the valid visit total from the player’s remaining score. A missed dart scores zero. Keep the landing values separate from the remaining-score calculation so an error is easier to trace.

Example: subtract a three-dart visit

Starting at 501, imagine treble twenty, single twenty, and single five. The visit is 60 + 20 + 5 = 85, leaving 416. Record both the 85 and the remaining 416 if you are keeping a paper history.

On the next visit, a score of 60 leaves 356. Announce or confirm the visit before retrieving the darts so a doubtful landing can be checked while the evidence is still on the board. Keep players’ columns clearly separate instead of recording totals in an unlabeled list.

A bust cancels the visit

Under standard double-out 501, a visit busts if it takes the remaining score below zero, leaves one, or reaches zero without the final scoring dart being a double. The player returns to the score at the beginning of that visit, and the turn ends.

For example, with 32 remaining, a single twenty followed by a single twenty would go below zero. The visit is a bust, so the next turn still starts at 32. Do not keep the first dart’s reduction and merely ignore the second.

Reference: Darts Regulation Authority: current rulebook

Check the finish before entering the result

With 40 remaining, double twenty is a legal finish. Single twenty leaves 20, which can be finished with double ten on a later dart. An inner bull can finish 50 because it counts as double twenty-five.

If the winning double lands on the first or second dart, the leg ends; the player does not need to throw the remaining darts. In a scoring app, enter the valid result and any requested darts-used information carefully. Do not confuse a visit total with the count of darts thrown.

Use a paper score sheet as a checking exercise

Draw two player columns and keep visit scores beside the remaining total. Start both at 501. Write an original practice sequence: first player scores 85, second scores 60, first then scores 100. The remaining totals are 416, 441, and 316 respectively.

Check each subtraction independently before continuing. This separates arithmetic practice from throwing skill. A player can understand scoring without hitting a treble, and a strong throw does not prove the subtraction was entered correctly.

Now add a near-finish situation in a new leg: one player begins a visit at 32, hits single sixteen, then double eight. The valid total is 32 and the leg ends. Compare that with single sixteen followed by single sixteen, which reaches zero without a double and busts. The landing sequence matters, not just the sum.

Use the same examples in a scoring tool to check that you understand its entry method. Some interfaces ask for the visit total, while others can accept individual darts or additional finishing information. Read what the field represents before typing. A correct mathematical number in the wrong field can still produce the wrong scoreboard. Keep corrections visible and verify the remaining total before the next real throw.

Correct mistakes with a visible trail

If a score was entered incorrectly, restore the verified previous remaining score before continuing. On paper, make the correction legible. In an app, use its correction function rather than inventing a compensating score on the next visit.

At the start of each turn, confirm whose throw it is and what remains. Simple verification prevents a good checkout from being disputed because an earlier subtraction was wrong. A scoring tool reduces mental arithmetic, while players still need to verify the board and agreed rules.

• Add dart values before subtracting the visit.
• Apply the whole-visit bust rule.
• Confirm uncertain landings before retrieving darts.

Use a scoring tool with a clear entry convention

Confirm the starting score, player order, and finish format before entering the first visit. Read whether the interface asks for a turn total, individual darts, or additional finish information. Those are different entries, even when the numbers are all related to the same throw.

OneEighty supports 501 scoring and checkout information. Use it to organize the arithmetic while still checking actual landings. A tool cannot make a wrong segment call correct, and an entered total should not replace verifying a disputed dart on the board.

If you correct a score, restore the verified state before continuing and confirm whose turn comes next. Avoid inventing a compensating entry that leaves the history misleading. A visible correction makes the game easier to follow and preserves a useful record of what actually happened.

Practice arithmetic separately from aiming

Use a short written visit example to check ring values, addition, and subtraction before adding the pressure of a live game. Then practice a few simple remaining totals on the board. Understanding the result and landing the dart are separate skills, and both can be worked on deliberately.

Keep the agreed game format visible during casual play. Straight-in, double-in, double-out, and single-out describe choices that should not be mixed silently. Formal events use their own current rules, so follow the organizer’s instructions there.

After a practice visit, record the actual result rather than the route you hoped to throw. Recalculate from the new remainder when a dart misses its intended segment. A small accurate record is more useful than a long chart of imagined successful finishes.