The three relevant DREADMOOR SteamDB application IDs are 3629430 for the main game, 5219790 for the demo and 3808110 for the historical playtest. Choose the right entry before interpreting a build, player chart, review figure or download-size record. Data belonging to one application should not be transferred to another.
Choose the matching application
| Application | App ID | Status at the November 2, 2026 snapshot |
|---|---|---|
| DREADMOOR | 3629430 | Prerelease; Early Access planned for November 9 |
| DREADMOOR Demo | 5219790 | Separate demo released on October 6 |
| DREADMOOR Playtest | 3808110 | Historical testing application, marked disabled |
SteamDB is a third-party view of Steam information, not the game's developer or its purchasing checkout. The application identity is the first thing to establish when comparing its data with the current Steam store.
The Demo has its own App ID and identifies the main game as its parent application.
A search for the main title can also surface demo charts and playtest metadata. That is useful for finding related applications, but it is not evidence that their player totals, release states or package access are interchangeable.
Read a build record without inventing a version
A Steam build ID identifies a build record. It does not automatically translate into an in-game version string such as v0.3.32, and it does not explain what changed unless matching notes do so.
| Application | Captured public-branch build | Relevant record date |
|---|---|---|
| Main game | 26096345 | Updated October 21, 2026 |
| Demo | 26254439 | Built October 27; updated October 28, 2026 |
| Playtest | 25260127 | Built September 11; updated September 12, 2026 |
These are captured records, not a live latest-build claim. When using a history entry to investigate an issue, keep the application, branch, build and date together. A new record by itself does not prove a particular quest bug has been fixed.
Keep player and review figures with their app
A demo player chart measures activity in that demo application. It is not the main game's player count, a sales total or a forecast of how many people will buy Early Access.
Review information needs the same separation. The main title is prerelease at this snapshot; a demo rating should not be presented as a review score for a paid main-game release that has not yet launched.
A number copied from an older chart is also not a live number. Retain its date when discussing a historical observation rather than calling it the current population.
Separate depot sizes from storage requirements
A depot is part of Steam's content-delivery structure. Its captured on-disk or download size is a different field from the space requested on a store page, and both can change during development.
The current store requirements list 60 GB for the main game and 20 GB for the demo. Smaller depot figures do not cancel those requirements or guarantee the size of a future update. Use the store figure for the application's stated storage requirement and identify a depot figure as a dated content record if you need to discuss it.
Use metadata as a check, not a feature promise
Language tables, configuration entries and detected technologies can help identify an application, but a technical string is not a complete compatibility test. A launch entry or SDK name does not independently confirm native Linux, VR or a specific graphics-setting menu.
For a reliable comparison, check these four items in order:
- The application name and App ID.
- The branch and record date.
- Whether the field describes a store requirement, chart or delivered content.
- Whether a current announcement or in-game display supports the conclusion you want to draw.
That keeps build research useful without turning every metadata change into a promised feature or fix.