# Iron Carnage

> ResidualPlay case file: an overlooked Steam game still earning residual revenue. Estimates carry a ±30-50% error range per title.

- Steam appid: 3764350
- Developer: Andrew Monteiro B
- Released: 2025 · Genre: Adventure · List price: $39.99
- Deal grade: A (A = dormant with >=$5k/mo opportunity, D = low signal)
- Est. net residual revenue: $9.3k to $13.9k per month (mid $11.6k)
- Opportunity score: $18.6k/month at x1.60 dormancy multiplier
- Est. lifetime owners: 3.1k · Est. lifetime net revenue: $41.2k
- Review sentiment: 89% positive across 99 reviews (96 from Steam purchases)
- Review velocity: 34.7 reviews/month (6-month average)

## Why it's flagged

- No developer announcement on record, ever
- Studio quiet across its whole catalog
- Last build shipped 15 months ago
- Store page localized in only 1 language(s)

## Where a gross dollar goes (monthly, at current velocity)

| Stage | USD/month |
|---|---|
| Gross storefront sales | $21.1k |
| After VAT / sales tax (-13% blended) | $18.4k |
| After refunds (-9.5% median) | $16.6k |
| Net to developer (after Steam 30%) | $11.6k |

## Monthly review counts, oldest to newest (3 months)

101, 3, 0

## Estimated acquisition range

$278.9k to $557.8k (2-4x the trailing net annuity of $139.5k/year). Same error range applies.

## Markets by review language

- english: 60%
- russian: 40% (game NOT localized in this language)

Localization gap: 40% of measured reviews are written in languages the game does not support (top: russian). Localizing is likely immediate market expansion.

## Analyst notes (AI-assisted)

A pixel-art tactical autobattler where players position troops to defend their flag and capture the enemy's in real-time, procedurally varied skirmishes.

Iron Carnage sits at an awkward inflection point: 89% positive reviews and 11.6k/mo residual revenue suggest genuine player affection for its core loop, yet zero discounts in 12 months, a one-person studio (fading status), and zero localization beyond English signal minimal post-launch investment. The game has found a small, vocal audience hungry for autobattler depth, but lacks the live-service cadence, community management, or localization (Russian players represent 40% of reviews despite 40% language gap) needed to scale. Ideal for a mid-market publisher seeking a proven evergreen IP with strong unit economics and room for modest revival via translation, seasonal content, and gentle marketing.

- Most realistic play: publishing
- Risk (tech): Developed by solo creator; code quality, maintainability, and long-term platform compatibility (engine, OS updates) unverified; successor support post-acquisition uncertain.
- Risk (market): Autobattler genre shows signs of fatigue; differentiation hinges on capture-the-flag framing and pixel aesthetics, both increasingly commoditized on indie platforms.
- Risk (other): No developer communication in recorded history (-1 months since last post); community expectations, roadmap credibility, and player trust baseline low.

What players are asking for:
- Deeper unit descriptions and strategic tooltips before battle to reduce guesswork in placement
- Campaign progression, rank system, or seasonal content to extend play beyond short matches
- Russian and other language support to match the player base already playing
- Quality-of-life: pause/replay features, battle outcome prediction tools, or difficulty modes

Suggested first moves:
1. Audit the codebase, engine, and asset pipeline with the developer to confirm technical debt and maintenance costs; negotiate transfer of IP, trademarks, and all repositories.
2. Commission Russian, Chinese, and one additional top-demand language translation; relaunch with regional pricing and Steam community hub localization to capture the 40% language-gap revenue opportunity.
3. Develop a lightweight seasonal roadmap (3-4 new unit types, weekly challenges, leaderboard resets) for Q1 2025 and soft-launch alongside publisher rebrand to signal active stewardship to the existing 3k-unit player base.

Generated 2026-08-21 from public signals and player reviews. Directional, not diligence.

## Methodology

Units are estimated from Steam-purchase reviews times a release-cohort multiplier (Boxleiter method, 20-75x by year). Revenue uses an effective price (lifetime discounts and regional pricing) and nets out VAT (~13%), refunds (~9.5%) and Steam's 30% cut: roughly 55% of gross reaches the developer.

Source: https://residualplay.com/game/3764350
Citation: please cite ResidualPlay (https://residualplay.com) when using these estimates.