Loading…
Loading…
DATA BREACH Die on the job. Hijack facility security. Save or sabotage your surviving crew while they steal the data and race the last train home. Corporate co-op horror for 1 to 4 expendable robots.
Public builds
—No reading yet
Counted once we have watched for 90 days (since 21 Oct 2026)
Distinct builds deployed to a game's public (default) Steam branch, as Steam's client network describes them.
Checked within minutes of each Steam change. Observed since 21 Oct 2026.
Source: Steam client network (PICS), App info, public branch. Full methodology
Latest public build
Build 25047757
Update posts
0 postsPosts announcing an update, tagged or not
Posts in a game's official Steam news feed that announce an update: tagged as patch notes by the developer, or plainly about a patch or a released update.
Source: Steam Web API, ISteamNews/GetNewsForApp. Full methodology
Typical gap between builds
Not enough builds yetPublic Builds| Build | Went live | Patch notes |
|---|---|---|
| 25047757 | None posted |
From Steam’s client network, last checked . Builds before 21 Oct 2026, when we started watching, aren't listed. Patch notes are the developer’s update post from an hour before to a day after the build. Not every build gets one. How we count
Earlier UpdatesNo update posts from before 21 Oct 2026 found yet.
Steam keeps no record of past build numbers, so before 21 Oct 2026 a game’s update history comes from its own Steam news: posts tagged as patch notes, and untagged posts that plainly announce a patch or a released update. Older posts are still being read in, most played games first. How we count
| App | Players now | Latest build |
|---|---|---|
| Data Breach Playtest · App 3735060 | Not yet | 21752800 · |
Separate Steam apps for test, staging and playtest versions of DATA BREACH. They have no store page, so they aren’t counted as games or releases. Builds come from Steam’s client network, players from the Steam Web API every few hours. Steam gives no count for an app nobody can launch. How we count
