Rust Entity Management: Stopping Performance Degradation Between Wipes

Published on

Rust server performance degrades over a wipe cycle as entities accumulate. Here's how to monitor and manage entity counts to maintain TPS throughout the cycle.

Written by Alex van der Berg – Infrastructure Engineer at Space-Node – 15+ years combined experience in game server hosting, VPS infrastructure, and 24/7 streaming solutions. Read author bio →

Rust Entity Management: Stopping Performance Degradation Between Wipes

Day 1 of wipe: your Rust server runs at 60 FPS equivalent performance. Day 14 of wipe: the same server is struggling. Nothing changed in the configuration — what happened?

Entities happened. Every sleeping bag, every box, every deployable item placed by a player and every abandoned base is a physics and state object the server must track every tick. On Day 14 of a popular server, entity counts are often 5–10x higher than Day 1.

Understanding Rust Entity Count

Monitor entity count via RCON:

entity.stats

A healthy mid-wipe server should sit below 200,000 entities. Above 300,000, TPS degradation becomes player-noticeable. Above 500,000, the server will struggle to maintain smooth gameplay.

Key Entity Count Drivers

Sleeping bags — Each placed bag is an entity. Large base compounds can have 50+ bags per player. 100 players × 30 bags = 3,000 bag entities, all tracked.

Storage boxes — Every box is an entity. Zerg clans with 500-box bases add thousands of entities per base.

Turrets and auto-defense — Auto turrets are expensive entities. They track targets actively, consuming CPU every tick.

Deployed campfires and furnaces — Often forgotten after wipe-night. Thousands of abandoned campfires litter the map mid-cycle.

Configuration Tweaks to Slow Entity Growth

# In server.cfg
decay.upkeep_inside_building_privilege 1
decay.upkeep_period_minutes 60
decay.scale 1.0

# Deploy limits per player
limits.sleeping_bags 6
limits.storage_boxes 30
limits.turrets 4

Player entity limits prevent single clans from excessive entity deployment. These settings require the uMod/Oxide framework.

The Decay System as Entity Janitor

Rust's built-in decay system destroys unupkept structures. Ensure decay is enabled (it sometimes gets disabled accidentally):

decay.scale 1.0

A decay scale of 0 disables all decay, which will cause entity counts to spiral out of control within 4–5 days on an active server.

When to Force a Map Wipe Early

If entity counts exceed 500,000 mid-cycle and TPS has dropped below 20 server FPS, a forced early wipe is healthier for player experience than struggling through. Announce it in Discord 24 hours ahead: "Emergency wipe due to server technical issues — next wipe scheduled [date]." Players accept early wipes far better than sustained poor performance.

Space-Node's Rust hosting panel shows entity counts directly in the dashboard without needing RCON access.

Run your Rust server on Space-Node's Ryzen 9 hardware

About the Author

Alex van der Berg – Infrastructure Engineer at Space-Node – Experts in game server hosting, VPS infrastructure, and 24/7 streaming solutions with 15+ years combined experience.

Since 2023
500+ servers hosted
4.8/5 avg rating

Our team specializes in Minecraft, FiveM, Rust, and 24/7 streaming infrastructure, operating enterprise-grade AMD Ryzen 9 hardware in Netherlands datacenters. We maintain GDPR compliance and ISO 27001-aligned security standards.

View Space-Node's full team bio and credentials →

Launch Your VPS Today

Get started with professional VPS hosting powered by enterprise hardware. Instant deployment and 24/7 support included.

Rust Entity Management: Stopping Performance Degradation Between Wipes