Tokyo Xtreme Racer vs Wallpaper Engine
Reviews on Steam
Wallpaper Engine
59.5× more reviews
Critical reception
Wallpaper Engine
4.2pp gap
Cheaper at launch
Wallpaper Engine
$45.00 cheaper
Estimated sales (median)
Wallpaper Engine
36.6× more units (white-box estimate)
More recent
Tokyo Xtreme Racer
7 years apart
Tokyo Xtreme Racer
2025 · Racing
Genki Co., Ltd. · Genki Co., Ltd.
- Reviews
- 15,364
- Positive
- 94%
- Launch price
- $49.99
- Engine
- n/a
- Sales (median)
- 999K
- Net rev
- $28.5M
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, 13 only on Tokyo Xtreme Racer, 18 only on Wallpaper Engine.
Only Tokyo Xtreme Racer
RacingDriving3DControllerAutomobile SimArcadeVehicular CombatOpen WorldCombat RacingRPGGreat Soundtrack3D PlatformerMultiplayer
Shared
SingleplayerEarly Access
Only Wallpaper Engine
MatureUtilitiesAnimeSoftwareDesign & IllustrationAnimation & ModelingFirst-PersonNSFWIndieMemesCuteActionFunnyPhoto 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.0599K to 1.4M
units (median: 999K)
≈ $17.1M to $39.9M 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.