Bounty Train

Corbie Games · 2017 · $9.99 · Indie · deal grade B

Measured on 2026-10-05 20:31 UTC. The whole catalog is re-measured daily; a game that just launched can move fast between passes.

Estimated net residual revenue: $164 to $245 per month
Opportunity: $327 per month at x1.60 dormancy
Estimated lifetime owners: 72.9k
70% positive across 1740 reviews · 3.8 reviews/month

Why it's flagged

Developer silent for 7.5 years
Studio active elsewhere (3 titles tracked), so this one may welcome a partner
Last discounted 0 months ago, 10 sales in the last 12 months
Proven demand elasticity: x1.5 review velocity during past deep sales

Analyst notes (AI-assisted)

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

A 2017 indie train-management sim with light roguelike and RTS combat elements set in the American Old West.

Bounty Train holds solid residual monthly revenue with a stable, if small, player base and respectable 70% positive sentiment. The title shows the classic indie archetype: niche appeal, modest engagement, and enough genre-mix friction to limit mainstream adoption, but sufficient depth to retain dedicated players who describe it as a "chill" time-sink. For a revival-minded publisher, the game's low-engagement ceiling and repetitive progression loop suggest content expansion (new routes, mechanics, difficulty modes) could unlock appeal to the $5-10 impulse-buy segment that discovered it on sale. Acquisition of the catalog alone is unlikely to move the needle; watch the title as a test case for low-cost live-service revival or catalog bundling. Most realistic play: watch.

Risk: Genre-mixing (train sim + RTS + roguelike) creates friction; players report steep learning curve and early churn after 20-30 hours.
Risk: Zero promotional discounts in 12 months and no developer posts in ~89 months suggest the title is in quiet maintenance; revival would require new content investment.
Risk: Repetitive fetch-quest design is the single most cited complaint; extending playtime without structural refresh may not move engagement metrics.

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