Spades Scoring, Explained

Spades scoring multiplies a made bid by ten, which means a single trick's difference between making and missing a bid is worth far more than the trick itself — and bags, which look harmless in the moment they're earned, are actually a delayed penalty building quietly in the background.

The core scoring rule

A partnership that takes AT LEAST as many tricks as their combined bid scores 10 points per trick bid, plus 1 extra point for each overtrick (a trick taken beyond the bid — a "bag"). A partnership that falls short of their bid scores nothing, and loses 10 points per trick of the bid instead.

Worked example 1: a bid made exactly

A partnership bids a combined 7 (say, 4 and 3 from the two partners) and takes exactly 7 tricks. Score: 7 × 10 = 70 points, with zero bags added since there were no tricks beyond the bid.

Worked example 2: the same bid, but with overtricks

Same combined bid of 7, but the partnership actually takes 9 tricks — 2 more than bid. Score: 7 × 10 (the bid) + 2 (the two overtricks, 1 point each) = 72 points. Those 2 extra points look like a pure bonus in the moment, but they also add 2 bags to the partnership's running bag count, which matters later.

Worked example 3: a bid that fails

A partnership bids 6 combined but only takes 4 tricks. Because the bid wasn't met, they score NOTHING for the tricks actually taken — instead, they lose 10 points per trick BID, not per trick missed: 6 × 10 = -60 points, regardless of the fact that they did take 4 real tricks during play.

Worked example 4: a made nil, scored completely separately from the team bid

One partner bids nil (betting to take zero tricks personally) while the other bids 5 for the partnership's normal contribution. The nil succeeds — that partner genuinely takes zero tricks — scoring a flat 100 points on its own. The partner's separate bid of 5 is scored completely independently: if their side collectively takes exactly 5 tricks between the non-nil partner's tricks and whatever the nil partner accidentally avoided taking, that's 5 × 10 = 50. Combined score for the partnership this hand: 100 + 50 = 150.

Worked example 5: a failed nil, costing the same 100 points in reverse

Same setup, but this time the nil-bidding partner accidentally wins one trick partway through the hand. The nil fails, costing -100 points — and that single trick the nil bidder won still counts as a bag against the partnership's normal bid total, on top of the -100 penalty, rather than being excluded from the count entirely.

Worked example 6: bags accumulating across several hands to the penalty threshold

A partnership's bag count from hand to hand: 3 bags after hand 1, 3 more after hand 2 (running total: 6), then 2 more after hand 3 (running total: 8), then 3 more after hand 4 — crossing the 10-bag threshold at a running total of 11. The instant that threshold is crossed, a 100-point penalty is charged against the partnership's score, and the bag count typically resets down by 10 (leaving 1 bag carried forward), not all the way to zero. This penalty has nothing to do with any single hand's bid or result — it's purely a consequence of accumulated overtricks across several separate hands.

Worked example 7: a blind nil doubling both the risk and the reward

A partnership trailing badly decides to bid blind nil — declared before that player has even looked at their hand. It succeeds: 200 points, double the value of a sighted nil. Had it failed instead, the partnership would have lost 200 points, also double the ordinary nil penalty — the same all-or-nothing structure as a normal nil, just with the stakes doubled in both directions to match the added risk of bidding without any information at all.

Worked example 8: why a bid of zero on the normal side is rarely worth it

A partner considers bidding 0 on their normal (non-nil) portion of a combined bid, reasoning that a low bid is safer than a high one. But a made bid of 0 combined with a partner's 4 only scores 4 × 10 = 40 total for the partnership — while a failed higher bid loses more, a made higher bid also earns proportionally more, since the entire scoring structure is bid-times-ten either way. Bidding artificially low doesn't reduce risk the way it might in a game with partial credit; it simply caps the maximum reward available from that hand.

Worked example 9: comparing two hands with identical trick counts but different bids

Hand A: bid 5, take 5 — scores 50. Hand B: bid 3, take 5 — scores 30 (3 × 10) plus 2 bags (2 points), for 32, despite taking the exact same 5 tricks as Hand A. The bid itself, not the raw trick count, is what the scoring actually rewards — taking more tricks than a low bid predicted adds only marginal bag points, while an accurately bid hand of the same size scores substantially more for the identical result on the table.

The fastest way to total a hand

1. Score any nil or blind nil bids first and separately (+100/-100 for nil, +200/-200 for blind nil), independent of the partnership's own bid outcome.
2. Check whether the partnership's combined normal bid was met — if not, subtract 10 points per trick bid and stop there.
3. If the bid was met, add 10 points per trick bid, plus 1 point per overtrick (bag) taken beyond it.
4. Add this hand's bags to the partnership's running bag total, and check whether it's crossed 10 — if so, apply the 100-point penalty and carry the remainder forward.

For the bidding phase, spade-breaking rule and how a nil bid actually gets protected during play by the rest of the partnership, see the full Spades rules and the dispute page for the bag-reset and blind-nil-eligibility questions argued most often at real tables.