2017 Offseason Salary Cap Digest: Sacramento Kings

After flirting with possible playoff contention in the first half, the Kings opted instead for a full rebuild, sending DeMarcus Cousins to New Orleans over the All-Star break for what was widely considered to be an underwhelming trade package. But with Buddy Hield playing well down the stretch and the Pelicans’ pick turning into a top-10 selection, the return on Cousins doesn’t look too bad anymore — and some lottery luck ensured that Sacramento will also have a top-five pick in June. Hitting on those two lottery selections would help get the Kings’ rebuild get off to a great start.

Here’s where things currently stand for the Kings financially, as we continue our Offseason Salary Cap Digest series for 2017:

Guaranteed Salary

Player Options

Team Options

  • None

Non-Guaranteed Salary

  • Arron Afflalo ($11,000,000) — Partial guarantee. Guaranteed portion noted above.2
  • Anthony Tolliver ($6,000,000) — Partial guarantee. Guaranteed portion noted above.1
  • Total: $17,000,000

Restricted Free Agents

  • Ben McLemore ($4,187,598 qualifying offer / $10,022,205 cap hold)
  • Total: $10,022,205

Cap Holds

Trade Exceptions

Projected Salary Cap: $101,000,000

Maximum Cap Room: $55,844,782

  • The Kings have cap holds for a pair of top-10 draft picks to account for, but their guaranteed contracts don’t amount to much. Taking into account their draft picks, guaranteed salaries, and three cap charges for empty roster spots, the Kings would have just $45,155,218 in team salary. However, that would hinge on Galloway turning down his player option, Afflalo and Tolliver being waived, every free agent leaving, and Bogdanovic not being signed this season, so Sacramento is unlikely to have quite that much room heading into free agency.

Footnotes:

  1. Tolliver’s salary reportedly becomes fully guaranteed after June 1.
  2. Afflalo’s salary becomes fully guaranteed after June 23.

Salary information from Basketball Insiders and The Vertical was used in the creation of this post.

View Comments (2)