Preparing the interactive tool. Please wait; the guide and worked examples remain available below.

Private, browser-local planner · user inputs only

TC reserve and electricity paper checks

This page does not connect to Rust, your server, a save file, or an account. It does not read live upkeep, server multipliers, source output, or circuit state. Enter values you can see in-game or have confirmed with your server admin. Nothing is uploaded or saved by this tool.

Tool Cupboard reserve estimate

Enter each material's displayed cost per 24 hours from your own TC. The result assumes the multiplier is linear and applies it to the UI amount you entered. If the TC display already includes server settings or a visible group tax, use 1.0 to avoid applying the same adjustment twice. This is an estimate, not Rust's upkeep engine.

Illustrative reserve for 36 hours
  • Material shown in TC: 0 units (based on your 0/24 h input)
  • Second material (optional): 0 units (based on your 0/24 h input)

Round-up is used so a fractional estimate does not understate your entered target. Recheck the TC after group or server changes; current in-game values override this estimate.

Electrical branch paper budget

Enter observed source output, the Branch Out setting, and the combined loads you intend to feed from that branch leg. The checks below compare your numbers only; they do not model Rust component active usage, switch state, battery discharge, wire topology, or demand changes.

Enter circuit readings to compare

These comparisons assume every listed consumer belongs to Branch Out and the numbers share one unit. Verify exact ports, settings, component behavior, and live readings in Rust before rewiring.

Official references: TC upkeep display · Electrical Branch ports. No server API, analytics, or persistent storage is used.

1. Separate permission from decay

A cupboard can protect connected building blocks from decay while your character is not authorized to build, or your character can have building privilege while the cupboard has insufficient upkeep. One symptom does not prove the other is working.

What you seeCheck firstWhat it tells you
BUILDING PRIVILEGE appears, but placement is blockedCheck the placement message and the specific blockerPrivilege is present; another building rule may prevent that placement.
No BUILDING PRIVILEGE indicatorApproach the cupboard and check authorization; walk across the footprintYou may be outside its projected footprint or not authorized.
TC says base is not protected / decayingInspect its material costs, stock, and time-left displayPrivilege alone does not mean upkeep is paid.
A nearby structure decays while the main base does notCheck whether foundations connect it to the protected buildingSeparate buildings need their own cupboard or a connected footprint.

2. Restore authorization without guessing the radius

  1. Go to the Tool Cupboard and use its interaction menu to authorize. Facepunch says placement authorizes the placer; teammates need to authorize themselves separately.
  2. Walk through the exact area where the building plan is blocked. The BUILDING PRIVILEGE indicator is a practical boundary check; do not infer the shape from a simple circle around the cupboard.
  3. If an authorized teammate still cannot build, have them inspect their own indicator and re-authorize at that cupboard. Confirm they are not working on a disconnected external structure.
  4. Read the placement preview and the game’s blocker message. TC authorization does not override every placement restriction, and unauthorized twig floors or ladders can behave differently from other building pieces.

3. Read the upkeep panel as the current calculation

Open the cupboard inventory and record the displayed resource categories, cost per 24 hours, time protected, and any visible upkeep tax. Those values are more useful than a generic ‘small base’ estimate. Doors and building blocks affect upkeep; the Facepunch guide says ordinary deployables such as sleeping bags do not.

  1. Write down each material row exactly as the game displays it; do not combine unlike materials into one total.
  2. Check the visible group tax by hovering over the upkeep cost if the interface offers that detail. The September 2026 group-scaling update counts current and recently removed authorizations and code-lock access, so removing someone just before checking may not immediately erase the tax.
  3. If your server advertises an upkeep multiplier or custom decay settings, record it from that server’s rules/admin. Do not apply an extra multiplier to a TC reading that already reflects it.
  4. Reopen the TC after any group, building, or server-setting change; the screen is the baseline for your next reserve plan.

4. Plan a reserve for the time you will be away

Use the local reserve planner below only as arithmetic on numbers you enter. It assumes a straight-line multiplier because the owner enters that assumption; it does not know the server’s config or apply Rust’s internal group-scaling rules. If the in-game 24-hour display already includes the server’s settings, leave the multiplier at 1.0.

SituationGood next moveAvoid
A duo base’s TC total changed after a larger group joinedRe-read the live 24-hour cost and tax detailReusing an old solo screenshot or base-size chart.
Community server says upkeep is 0.5×Ask whether the TC UI is already modified; compare its displayed rateMultiplying a server-adjusted display by 0.5 again.
You are short one material but have plenty of anotherAdd the missing displayed category separatelyTreating total value as interchangeable upkeep.
An external wall or disconnected building is decayingCheck coverage/connection and its own TC protectionAssuming the main TC protects every nearby structure.

5. If the panel and the server rules disagree

Record the server name/type, patch date, visible TC values, group size, and the exact decay message. The official console-command reference documents server-side upkeep controls, but a player should not assume a command value is active on a community server. Ask that server’s admin to confirm the effective setting. Steam discussions are anecdotal context, not a substitute for the TC UI or administrator confirmation.

Before you play

  • I checked the live Rust UI and current server/platform scope.
  • I recorded the relevant settings rather than relying on a generic community build.
  • I changed one variable at a time and verified the result in game.

Frequently asked questions

Does this guide inspect my server?

No. It uses published Facepunch sources and values that you verify in your own UI.

Can server settings change the outcome?

Yes. Console parity, community-server multipliers, plugins and custom settings may differ; the live server rules and UI are authoritative.

Sources & revision notes

Editorial revision: November 6, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

  1. Facepunch Rust Wiki — Tool Cupboard, building privilege, decay and upkeep (Official)

    Facepunch documentation or update notes. Verify against the live in-game UI and server settings; this guide does not read a Rust server.

  2. Facepunch Rust Wiki — Tool Cupboard item (Official)

    Facepunch documentation or update notes. Verify against the live in-game UI and server settings; this guide does not read a Rust server.

  3. Facepunch — Breach and Clear update (September 3, 2026), upkeep group scaling (Official)

    Facepunch documentation or update notes. Verify against the live in-game UI and server settings; this guide does not read a Rust server.

  4. Facepunch — Rust patch history (Official)

    Facepunch documentation or update notes. Verify against the live in-game UI and server settings; this guide does not read a Rust server.

  5. Facepunch Rust Wiki — server upkeep commands (Official)

    Facepunch documentation or update notes. Verify against the live in-game UI and server settings; this guide does not read a Rust server.

  6. Steam discussion — community server advertising TC upkeep x0.5 (Community)

    External user-generated context, possibly patch- or server-specific; not official mechanics authority or GamerWin testing.

  7. Steam discussion — decay settings on a privately hosted server (Community)

    External user-generated context, possibly patch- or server-specific; not official mechanics authority or GamerWin testing.

What changed in this revision

November 6, 2026: first publication, based on current Facepunch sources; no live server or in-game test was performed.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.