Current Steam players
The official Steam Current Players API returned 9,479 players for App ID 3079210 during the August 14, 2026 research check. That number was a momentary sample, not a permanent value. The live page should request or cache the current result and display its update time.
If the API fails, show the most recent successful value and timestamp instead of zero. A network failure is not evidence that nobody is playing. The page should also identify the source as Steam rather than presenting a large number without platform context.
Release App ID versus Playtest
The release uses Steam App ID 3079210. The earlier Hell Let Loose Vietnam Playtest uses App ID 3780860. Their current players and peaks describe different applications and must not be added together.
After launch, a residual Playtest number may represent testing access, internal activity, or a separate test period. It is not part of the retail game’s current Steam concurrency. Every chart and API request should display the App ID beside the title.
What the Steam number excludes
Steam does not count players using Epic Games Store, Microsoft Store, PlayStation 5, or Xbox Series X|S. The game supports those platforms and cross-platform multiplayer, so Steam concurrency is only one visible segment. No reliable public source in the collected research exposes a complete live total across all platforms.
Do not multiply Steam by a guessed platform ratio. Do not call the Steam peak the “total game peak” without qualification. The correct label is “Steam concurrent players,” followed by the retrieval time.
24-hour and all-time peaks
SteamDB can display current, 24-hour, and historical peak data for the release App ID. Those values change and should be fetched or refreshed instead of copied into static MDX. A chart should explain timezone and source behaviour, especially around launch-day spikes.
The earlier Playtest reached its own all-time peak, but that value belongs on a separate comparison series. It can provide historical interest as long as the legend and App ID prevent a reader from interpreting it as retail concurrency. Never merge the two lines.
Reviews are a different metric
Steam review count, positive ratio, followers, Twitch viewers, and concurrent players measure different actions. During the site-data check, the store showed a Mixed review state and a growing review total. Those values should not be used as a substitute for current players.
Likewise, Twitch viewers do not equal owners or active players. A launch trailer’s views do not measure retention. Keep each metric in its own labelled module and give it a current source and timestamp.
Recommended page implementation
The static article should explain the methodology, while a small Worker endpoint retrieves the official current-player API and caches it for 10–15 minutes. Historical peaks can be shown through a permitted embed or separately maintained data source. Static assets remain available even if the dynamic endpoint fails.
The response should include value, source, appid, and updatedAt. The front end should format the timestamp in the reader’s timezone but preserve an exact machine-readable value. Do not cache a launch-day number indefinitely in the generated HTML.
How to interpret launch activity
Launch produces unusual peaks, review bursts, server queues, and rapid patches. One hourly sample cannot establish whether a game is growing or declining. Compare consistent time windows and note sales, weekends, updates, or free events before drawing a trend conclusion.
Even a longer Steam trend remains incomplete because crossplay can distribute players across several storefronts and consoles. Use the data to answer “how many are currently on Steam?” rather than “is the game alive everywhere?” The latter requires evidence that is not publicly available here.
Disclosure shown beside every chart
Steam only. Excludes Epic Games Store, Microsoft Store, PS5, and Xbox. Release App ID 3079210; Playtest App ID 3780860 is not included. Values change continuously and are labelled with their retrieval time.
This disclosure is not optional fine print. It prevents the most common player-count error: turning one accessible platform counter into a total for the whole cross-platform game.