Why is my Rust server lagging, and what actually helps? Rust lag usually comes from the number of entities and the size of the map, not from one magic setting. Wipe on a regular schedule, size the map to your player count, keep plugins lean, avoid very frequent saves, restart regularly, and measure server FPS with the fps command under real player load before and after every change.
How do I check my Rust server’s performance?
Type fps in the server console to see current server FPS. That is the number to watch, not tickrate.
Check it at peak player count. An idle server always looks fine, so a reading taken at 3am tells you nothing about Saturday night.
Tip: Change one setting at a time and check fps again under similar load. Several guides disagree on exact values, so your own measurements are the tiebreaker.
Does map size affect Rust server lag?
Yes. A bigger map means more monuments to simulate, more AI to spawn, more terrain to keep loaded, and a much higher ceiling for player-built entities. Entity count grows through a wipe cycle, which is why servers feel smooth after a wipe and worse by the end.
Match the map to your player count. Many guides suggest 3000 to 4000 as a starting point for most servers, and regular wipes keep entity counts down. Use your panel’s scheduler to automate them.
| Setting | File | Default | Recommended |
|---|---|---|---|
server.worldsize |
Rust convar | your current size | 3000–4000 for most servers |
Why does my Rust server hitch every few minutes?
Every save impacts players. The default server.saveinterval is 600 seconds, and a longer interval means fewer hitches.
The trade-off is progress. If the server crashes, you lose everything since the last save, so most guides stay in the 300 to 600 second range.
| Setting | File | Default | Recommended |
|---|---|---|---|
server.saveinterval |
Rust convar | 600 | 300–600, longer = fewer hitches |
Do plugins and restarts matter?
Plugins are a common hidden cost. Each one adds work every tick, so remove what you do not use and add new ones one at a time while watching fps. See our uMod plugin guide for installing them from the panel.
Regular restarts help too. Without them, long-running servers can see memory growth, rising CPU load, and degraded performance. Your panel’s scheduler can restart the server on a timer.
Should I change server.tickrate or fps.limit?
Usually not. Tickrate is read at startup and is not the same as server FPS. Guides disagree on whether raising it improves anything, and some say it only burns CPU. Do not chase it.
fps.limit caps server FPS so the server does not waste CPU. A range of 30 to 60 is commonly suggested, but a cap will not make a struggling server faster, and command names vary between versions, so confirm yours first.
Tip: Seeing players struggle to find your server at all? That is usually ports, not performance. See our Rust networking setup guide.
Frequently asked questions
How do I check server FPS on a Rust server?
Type fps in the server console. Check it at peak player count, because an empty server always looks healthy.
What map size should I use for a Rust server?
Many guides suggest around 3000 to 4000 for most servers. Bigger maps add monuments, AI, and a higher ceiling for player-built entities, so match the size to your player count.
Does a higher tickrate make a Rust server better?
Not reliably. Tickrate is read at startup and is not the same as server FPS, and guides disagree on whether raising it helps at all. Watch server FPS instead.
Do Rust plugins cause lag?
They can. Every plugin adds work, so remove the ones you do not use and add new ones one at a time while watching server FPS.