Rust Server Lag and Low FPS Fix (What to Check First)

To fix a laggy Rust server, first run serverinfo in the console and look at the server framerate and entity count. Low server FPS with a high entity count means too many buildings and deployables, so let decay work and clear abandoned bases. Low server FPS with a normal entity count usually means a heavy plugin. Spikes every few minutes on the dot are world saves. If server FPS is fine, the lag is the player's connection or their own PC, not your server.

Server lag or client lag?

This is the first question, because the fixes are completely different.

Players say "lag" for all of these. Ask whether it happens to everyone at once. If it does, it is yours to fix.

How to check server FPS and entity count

Run these in the server console:

serverinfo
server.fps

serverinfo prints one line with players, queue, EntityCount, Framerate, memory and uptime. server.fps prints just the framerate.

Our rough rules of thumb:

Server FPS is not client FPS. Your server running at 40 does not cap anyone's screen at 40. It means the world simulates 40 times a second, and below about 30 players start to feel it.

Write down the entity count at the start of a wipe and check it again a week in. Entities are every building block, door, box, furnace, sleeping bag, dropped item and NPC. The count climbs all wipe, and it is the single best predictor of a laggy late wipe.

Cause 1: Too many entities

Rust has to simulate and network every entity. Large bases, sprawling farms and abandoned compounds add up.

What to do:

• Keep decay on. decay.scale 1 is the default for a reason. Decay removes bases that nobody is upkeeping. Turning it off on a public server means every base ever built stays until the wipe.
• Keep upkeep on. decay.upkeep true makes large bases cost more to maintain, which naturally limits megabases.
• Clean up after cheaters and quitters. entity.countby <steamid> shows how much one player built. entity.deleteby <steamid> removes all of it. Back up first, there is no undo.
• Wipe more often if you need to. A weekly or biweekly wipe is the most reliable entity limit there is. Busy servers wipe weekly partly for this reason.

Cause 2: Save hitches

Every autosave pauses the server for a moment, and the pause grows with the entity count. If players report a freeze every 5 or 10 minutes like clockwork, that is it.

server.saveinterval sets the gap in seconds. Rust's default is 600, and we start our servers at 300. On a huge late wipe server, a longer interval means fewer hitches but more lost progress after a crash. 300 to 600 is the sensible range. Do not go below 300.

Cause 3: Heavy plugins

Every Oxide or Carbon plugin hooks into game events. A badly written or overloaded one can cost more than the whole vanilla game.

Find the culprit:

oxide.plugins

or on Carbon:

c.plugins

Both list your plugins with their hook time. Look for one that is far above the rest. Then unload it (oxide.unload Name or c.unload Name) for an hour and watch server.fps. If FPS recovers, you found it: check its config for something expensive (short timers, huge radius checks, many UI refreshes) or replace it.

Usual suspects: big event plugins, plugins that scan every entity on the map, UI plugins that refresh every second for every player, and logging plugins writing on every action.

Cause 4: Not enough RAM

Rust's memory use grows through a wipe as players build. When the server runs out, it starts swapping or crashes outright. Watch memory in serverinfo or your panel graph across a wipe.

If memory sits near the limit by mid wipe, a bigger plan is the real fix. Everything else is buying time.

Cause 5: Map size and NPC load

A bigger map than you need means more resources, more animals and more monuments with scientists, all simulated whether anyone is near them or not. A 4500 map for 20 players is paying for empty space. Next wipe, size down. See how to change Rust map size and seed.

Settings you should not touch

• server.tickrate: default 10. Raising it adds work for every connected player and makes things worse on a server that is already struggling.
• fps.limit: the server's framerate cap. Raising it does not give you FPS the CPU cannot produce, and lowering it saves CPU but never fixes lag.
• Random "performance convars" from forums: many are from years ago and either do nothing now or quietly break something.

When it is the player's PC

If server FPS is healthy and only some players complain, it is client side. Rust is heavy on the client. Point them at lowering graphics quality, draw distance and grass, closing background apps, and checking their own ping in the F1 console. Players far from the server's region also see more rubber banding, which no server setting fixes.

The easy way

On GamezServers, the save interval is a field in Settings, the console is right in the panel for serverinfo and plugin checks, and upgrading RAM is a plan change in Settings, prorated, applied after a restart. If you have done the checks and still cannot find it, email support@gamezservers.com with your serverinfo output and we will look at it with you. For lag in general across games, see why is my game server lagging.

FAQ

What is a good server FPS for Rust?

Above 30 is fine for most servers and above 60 feels smooth. Below 30, players start to notice rubber banding, and below 15 the server feels broken.

Why does my Rust server lag every 5 minutes?

That is the autosave. Each save pauses the world briefly, and the pause grows as the entity count grows. Clean up entities, or move server.saveinterval toward 600.

Does a higher tick rate fix Rust lag?

No. Raising server.tickrate adds CPU load for every player. On a server that is already struggling, it makes things worse.

How many entities is too many on a Rust server?

There is no fixed number, because it depends on the CPU and plugins. Track your own count against your server FPS through a wipe, and you will see where your server starts to struggle.

Will restarting fix a laggy Rust server?

A restart clears memory and can help for a while, especially with a leaky plugin. It does not lower the entity count, so if buildings are the cause, the lag comes back.