TODAY’S PAPER | March 06, 2026 | EPAPER

Slay the Spire 2 reaches 177k concurrent players on Steam after early access launch

Slay the Spire 2 surpassed 177,000 concurrent players on Steam shortly after entering early access


Pop Culture & Art March 06, 2026 1 min read
Photo: Steam

Slay the Spire 2 has recorded a strong debut on Steam after launching in early access, reaching 177,000 concurrent players on the platform shortly after release.

The figure was still rising at the time of reporting, setting a new concurrent player record for a roguelike game on Steam.

The sequel to the deckbuilding roguelike Slay the Spire launched on March 5 on PC through early access. Within its first hour on the platform, the game surpassed 100,000 concurrent players.

Approximately 90 minutes after launch, the player count had climbed to around 135,000, continuing to increase throughout the day.

The total later exceeded 150,000 and eventually reached about 177,000 concurrent players. According to the reported figures, this placed the game fourth among the most-played titles on Steam at the time, behind Counter-Strike 2, Dota 2 and Arc Raiders, and ahead of Rust.

Earlier reports noted that the previous record for the highest concurrent player count for a roguelike on Steam was held by Hades 2 at 112,000 players.

More recently, Mewgenics surpassed that total during its launch weekend with 115,000 concurrent players before being overtaken by Slay the Spire 2.

The original Slay the Spire launched in early access in 2017 and is widely credited with establishing the modern roguelike deckbuilder format by combining card-based strategy with dungeon crawling mechanics.

Slay the Spire 2 entered early access with more than 100,000 wishlists, indicating significant interest ahead of release. Additional content, including new cards, enemies and environments, is planned as development continues before the full launch.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ