Data basis: your own butchering results, logged on the day you get them. Written 2026-08-16. No animal on this page has a claimed yield number. The reason is the friction that prompted it.
Two threads a day apart made the same complaint from opposite directions. “How to butcher Turkeys?” on 14 August 2026 was a player who couldn’t get the process to work at all. The other, the same week, was blunter: the wiki said a large boar could be hooked, and it didn’t match what the poster actually saw happen in their own Build 42 game. Put those next to each other and the lesson isn’t “here is the corrected number” — it’s that a static yield table is exactly the kind of page that goes stale silently, and nobody notices until they’ve already acted on the wrong number.
Why wiki yield numbers do not match yours
Every other page on this site that publishes a table says so because it’s our own worked comparison or our own explicit model, labelled as such. Butchering yields are neither — they’re a game-internal value we cannot extract or verify, and copying one from a source we can’t check would put us in exactly the position that prompted the boar-hooking complaint in the first place: a number on a page, wrong for someone’s build, with no way for them to know it’s wrong until they’ve already relied on it.
Log it instead
The one dataset that is always current is the one you build from your own game. Every time you butcher something, log what you actually got. The averages below are computed from your entries only — nobody else’s, and never invented.
Log what you actually got
No entries logged yet on this device.
| Animal | Entries | Avg cuts | Range |
|---|
Saved in your browser only (localStorage on this device), never sent anywhere. This page publishes no yield numbers of its own — the wiki-mismatch complaints in the threads that prompted this are exactly why: a static table would just be one more page that might be wrong for your build. Your own log is the one dataset that cannot go stale on you.
Saved to your browser only, on this device. If you play across multiple machines, the log won’t follow you — that’s the honest trade-off of not running a server-side account system for what’s meant to be a lightweight tool.
What to log, and why it matters more than it sounds
- Tool used. Yield in Build 42 is reported by players to depend on whether you’re using a proper hunting knife versus an improvised blade — logging the tool lets your own data eventually show you whether that’s true for your game, rather than trusting a claim either way.
- Meat cuts specifically, separate from skins, feathers, and bones. Lumping “everything you got” into one number hides which part of the yield the wiki mismatch was actually about.
- Every attempt, not just the good ones. A log that only records successes isn’t an average, it’s a highlight reel, and it will overstate what you should expect next time.
Other numbers this site won’t reprint from a stale source
Yield tables aren’t the only place a remake or a build change quietly breaks a published number. The building-category search order for finding a generator runs into the same problem from a different angle — the old coordinate lists went stale when the map got rebuilt, so that page ranks building types instead of naming specific addresses it can’t stand behind, for the same reason this page asks you to log your own butchering results instead of trusting ours.
If you came here for the turkey question specifically
The 14 August thread’s core problem wasn’t yield, it was process — the butchering interaction not triggering at all. That’s a different failure mode from “I got fewer cuts than expected,” and no yield log fixes a process that never starts. If the interaction won’t start, check which of the three butchering gates you’re actually failing before assuming it’s a yield question — this page only helps once the interaction is actually working.
Sources
- Butchering — PZwiki — the page itself carries a stale-version warning (“This page was last updated for an older version of the current build”), which is direct evidence for this article’s core claim that published butchering numbers drift out of date between builds.
- Butchering chickens — Steam Community discussions — friction evidence of a player questioning whether their own butchering yield was normal, unable to check it against a reliable current number.
