Mini Metro vs Wallpaper Engine
Reviews on Steam
Wallpaper Engine
55.5× more reviews
Critical reception
Wallpaper Engine
2pp gap
Cheaper at launch
Wallpaper Engine
$5.00 cheaper
Estimated sales (median)
Wallpaper Engine
26.1× more units (white-box estimate)
More recent
Wallpaper Engine
3 years apart
Mini Metro
2015 · Indie
Dinosaur Polo Club · Dinosaur Polo Club
- Reviews
- 16,498
- Positive
- 96%
- Launch price
- $9.99
- Engine
- n/a
- Sales (median)
- 1.4M
- Net rev
- $8.0M
Wallpaper Engine
2018 · Casual
Wallpaper Engine Team · Wallpaper Engine Team
- Reviews
- 914,881
- Positive
- 98%
- Launch price
- $4.99
- Engine
- n/a
- Sales (median)
- 36.6M
- Net rev
- $104.3M
Tag overlap
10% shared , 2 shared tags, 18 only on Mini Metro, 18 only on Wallpaper Engine.
Only Mini Metro
StrategyPuzzleMinimalistSimulationTrainsCasualManagementRelaxing2DTransportationBuildingTouch-FriendlyMouse onlyDifficultGreat SoundtrackAddictiveReplay ValueTop-Down
Shared
IndieSingleplayer
Only Wallpaper Engine
MatureUtilitiesAnimeSoftwareDesign & IllustrationAnimation & ModelingFirst-PersonNSFWMemesCuteActionFunnyEarly AccessPhoto EditingSandboxHorrorGamingGame Development
Sales estimates
Both estimates use the same vv1.0 multi-factor Boxleiter method. Click "How is this calculated?" on either to see the per-factor breakdown.
Sales estimate
vv1.0841K to 2.0M
units (median: 1.4M)
≈ $4.8M to $11.2M net revenue (Steam cut + refunds + regional discount applied)
Sales estimate
vv1.022.0M to 51.2M
units (median: 36.6M)
≈ $62.6M to $146.0M net revenue (Steam cut + refunds + regional discount applied)
How comparison pages work
Verdicts are objective, they call out which game scores higher on a single measurable axis (reviews, price, sales estimate, recency). They don't claim "better." Tag overlap is computed from the public Steam tag list. Sales estimates use a multi-factor Boxleiter method whose formula is shown in full on each game's page.
Want a comparison that doesn't exist? Browse all games,
find two slugs, and concatenate them: /compare/games/<slug-a>/<slug-b>.
Both orderings render the same content; we canonicalise to alphabetical for SEO.