The Crust has published 147 official posts, 101 of them numbered releases, between 24 January 2023 and 19 September 2026 — from the first demo hotfix to Update 1.0.12. This is the complete record rather than a recent window: every official post, dated in UTC and linked to its original Steam announcement, including four numbering errors the developer published and never corrected.
- Official posts
- 147Whole feed, not a window
- Numbered releases
- 101Updates, patches, hotfixes
- Record spans
- Jan 2023 – Sep 20261,334 days
- Average gap
- ~13 daysOne release per fortnight
- Newest release
- 1.0.1219 September 2026
- Post-1.0 cadence
- 8 in 10 days10–19 September
- Oldest release
- 0.80.467Demo hotfix, 24 Jan 2023
- Date convention
- UTCSite-wide standard
What this page is, and what it deliberately is not
This is the game’s official Steam news feed, reproduced in full. Two decisions shaped it, and both matter for how you should read the tables.
It is paged, not sampled. Steam’s news endpoint returns a default slice of recent posts and a count field telling you how many exist in total. The two numbers did not match on the first attempt at this page, and the earlier version of this table covered only the most recent 38 posts while describing itself as the whole record. Paging the endpoint by date until it stopped returning new items produced 151 news items, of which 147 are the developer’s own.
Third-party posts are excluded, not silently mixed in. Four of the 151 items are articles by other outlets syndicated into the same feed — two from PC Gamer, one from GamingOnLinux and one from PlayGround.ru. They carry Steam news IDs and sit alongside official posts, which is exactly why a feed dump can look official when it is not. The rule used here is the feed’s own feedname field, because on this app every announcement URL carries the same externalpost prefix, so the URL cannot distinguish developer from journalist. Only the 147 official posts appear below.
The complete release history
Every official post the developer has published, newest first, grouped by year. Dates are Steam news timestamps in UTC. The Version column shows the version number named in the title, or “—” where the title names none — which is common, because the developer names some releases and numbers others. Type is not classified: the studio uses “Update”, “Patch”, “Hotfix” and “Hotfixes” inconsistently, and any category we invented on top of that would be our judgment rather than their record.
2026
44 official posts.
2025
27 official posts.
2024
52 official posts.
2023
23 official posts.
2021
1 official posts.
| UTC date | Version | Official post |
|---|---|---|
| 4 Sep 2021 | — | The Crust Announced at Showcase DevGAMM |
Four errors in the developer’s own numbering
An official release history is a document, and this one has handwriting in it. Four details are worth pointing out because they change how you read the list — and because each one is the developer’s, not a transcription slip on our side.
1. The same release is numbered two ways, in the same post. On 12 September 2026 the announcement title reads "Hotfix 1.06.1" while the heading inside the post reads "# Hotfix 1.0.6.1". Both were published by the developer and neither was corrected. Its position — between 1.0.6 and 1.0.7 — makes the intended number unambiguous. The title is reproduced exactly as published.
2. The post-launch sequence starts at 1.0.6, not 1.0.1. Across all 147 official posts there is no 1.0.1, 1.0.2, 1.0.3, 1.0.4 or 1.0.5. Either those builds were never released as separate public patches, or the numbering began at six. The notes do not say, and we are not going to guess — but if you find a site listing "The Crust 1.0.3 patch notes", it is reconstructing something the official record does not contain.
3. "Patch" is misspelled in a release title. The post of 3 February 2025 is titled "Path 0.96.10". It sits between a "Balance Fix" and a "Patch" in the same week's numbering, and its contents are an ordinary patch, so the intended word is not in doubt. We have left it as published, which is why it appears that way in the 2025 table.
4. Leading zeros appear and disappear inside the same series. The January 2023 demo line is published as "Demo Hotfix 0.80.467" and then as "Demo Hotfix 80.468", "80.469" and "80.470". The same happens in May 2024, where a numbered hotfix sits directly beside "Patch 90.41", and in October 2023 with "Update | v85.08". These are the same versioning system written inconsistently, not four different systems.
One more labelling note, because it trips up players tracking fixes. The word in a title describes the shape of the release as the studio saw it, not how disruptive it was. The developer has used “Hotfix” for releases containing dozens of balance changes and “Update” for releases containing a handful of fixes. If you are working out whether a given release matters to you, read its contents rather than its label — our troubleshooting page is organised that way for exactly this reason.
The cadence, measured rather than described
Three numbers put this game’s support rhythm in perspective, and all three come from the feed above rather than from anyone’s impression.
| Measure | Value | What it means |
|---|---|---|
| Numbered releases across the whole record | 101 over 1,334 days | A release roughly every thirteen days |
| Longest silence in the record | 223 days (26 Jan – 6 Sep 2023) | The demo era between festivals, not a finished game |
| Releases in the ten days after 1.0 | 8 (1.0.6 → 1.0.12) | Launch-window patching at full speed |
| Official posts in 2026 alone | 44 | The busiest year in the record so far |
The longest gap deserves a caveat rather than a headline. The 223 days between the last demo hotfix of January 2023 and the 0.83.52 patch of September 2023 came before Early Access existed, when the studio was between public builds and the feed carried festival announcements instead. For the period the game has actually been purchasable, the rhythm is much tighter: from the Early Access release on 12 July 2024 to 9 September 2026, the feed contains 82 releases across 789 days. The genuinely unusual gap in the live game is smaller and more recent — 59 days separate Patch 0.99.95 on 14 July 2026 from Hotfix 1.0.6 on 11 September 2026, a stretch containing only two posts, both announcements rather than releases. Set against a period where a patch every fortnight was normal, that is the clearest evidence in the feed that this team redirects effort into a large build rather than maintaining a steady drumbeat.
What one post can contain
The scale difference between a hotfix and a major update in this record is enormous, and the 1.0 post is the example worth reading closely because it contains the release in three layers at once.
The 1.0 announcement opens by admitting the problem of summarising it: “With over 2,000 commits made since Update 3, briefly describing every improvement included in version 1.0 is no easy task. We did our best!” It then runs through a “Key new features” section — Planning Mode, roads, the optimisation pass, wall panel styles, the completed story campaign, the online leaderboard, four new Sandbox maps, Sandbox 2.0, a Shower/Toilet module, the Anti-Meteorite Laser Cannon, global events, firing and salaries — followed by “A few more improvements” list of roughly twenty smaller items.
Two structural decisions in that post are worth copying as a reading habit.
It separates new features from the fix list. The April Big FPS and QoL update does the same thing with a heading that reads “Full Changelog v0.99.85” — the post and the changelog are distinct sections, and the changelog is where the fixes live. Update 3 also carries a “Full Changelog” heading. So when you open a page that appears to be about features, the fixes you actually need are usually further down and under a different heading.
It links backwards rather than repeating itself. 1.0’s “What has changed since Early Access?” section lists earlier major updates by name and links each to its own Steam post instead of restating their contents. That is how we know which updates the 1.0 notes consider the significant ones — and it is the developer’s own index, which makes it a better guide than any list assembled from outside.
Reading this history the way it is meant to be used
A version history is only useful if it changes what you do, so here are the three habits it supports.
Match your symptom to a patch, not to a date. If something is broken in your game, the question is not “when was this game last updated” but “which patch fixed this”. Every row above links to a post, and those posts name their fixes precisely — the word “Fixed” appears 775 times across the 147 official posts, which is what makes our troubleshooting page possible in the first place.
Assume your impressions have a build number. The most common form of outdated advice about this game is a complaint attached to a build that has since been patched. When you read something negative, the useful follow-up question is the date — and in this game’s first month the date is unusually decisive, because eight releases landed in ten days.
Expect the pattern to continue rather than to be a one-off. One hundred and one numbered releases across three and a half years is not a launch sprint, it is a working method. The same studio’s earlier rhythm included a 59-day quiet stretch immediately before 1.0, which suggests effort is redirected rather than reduced — the patches pause when a big build is coming, and then arrive in a burst.
If you only remember one thing
The Crust's most recent release in this record is 1.0.12 on 19 September 2026, and it arrived eight releases into a ten-day post-launch stretch. If you are troubleshooting anything, that version number — not the release date — is the thing to check first, because 775 documented fixes sit across the official feed and most of them are already in the build you are running.
Where this leaves you
Three things to carry forward. The feed contains 147 official posts, 101 of which name a version number, dated in UTC and linked to their originals — and it reaches back to a demo hotfix in January 2023, not to a recent window. Four numbering errors are the developer’s own — one release labelled two ways in a single post, a post-launch sequence that starts at 1.0.6 with nothing publicly below it, a “Patch” published as “Path”, and leading zeros that appear and vanish within one series. And the record begins in 2023 because that is where the releases begin, not because of any limit in how we retrieved it; before that the feed carries only the game’s 2021 reveal and its festival announcements.
What we have not done is pad the list. There is a temptation with a page like this to fill the gaps with third-party changelogs and reconstruct older patch summaries, and it would look tidier. It would also mean mixing records of unknown provenance with records we can date to the hour — which is the one thing this page can offer that a forum thread cannot.