ResidualPlaybeta Open the radar

SkyShard: City Battler

ItsBen321 · 2026 · $14.99 · Indie · deal grade B

Measured on 2026-09-26 20:50 UTC, 9 days ago. The whole catalog is re-measured daily; a game that just launched can move fast between passes.

  • Estimated net residual revenue: $2.1k to $3.2k per month
  • Opportunity: $3.4k per month at x1.30 dormancy
  • Estimated lifetime owners: 4.2k
  • 98% positive across 106 reviews · 21.0 reviews/month

Why it's flagged

  • Developer active, last post 0 months ago
  • Store page localized in only 1 language(s)
  • Last discounted 0 months ago, 4 sales in the last 12 months

Analyst notes (AI-assisted)

Note written 2026-08-29; the live figures above take precedence over any numbers in it.

An early-access auto-battler roguelike where you build armies on a tile-based city grid, combining units and items for synergies across 16 rounds of escalating strategy.

SkyShard is a quiet breakout in the competitive auto-battler space, attracting a devoted core audience (61% still actively playing) and maintaining exceptional sentiment (98% positive) with minimal marketing spend. The title demonstrates strong unit-economy design depth and zero monetization friction, generating solid mid-tier residual revenue despite launching only months ago. The game deserves consideration for a publishing refresh or IP licensing play: the developer roster is lean (two creators, one a recognizable name in card-game balance), and early player feedback suggests significant upside if discovery barriers fall or if the title receives platform promotion. Most realistic play: publishing.

  • Risk: Auto-battler genre is crowded (Hearthstone Battlegrounds, Backpack Battles, TFT); differentiation hinges entirely on build-synergy depth and dev iteration speed.
  • Risk: Two-person team means production velocity and live-service cadence may strain under publishing expectations or feature-expansion roadmaps.
  • Risk: Early access status requires either feature-complete roadmap transparency or risk of player churn if perceived as stalled development.

This case as Markdown · Estimates carry ±30-50% error per title.