How to fix Rust server lag, low server FPS and rubber banding

Rust lag usually comes from too many entities, a large map, heavy plugins or too many players for the available RAM and CPU.

Check server FPS

In the Console, run fps to see the server frame rate. A healthy server holds a steady number. Very low numbers during busy times mean the server is overloaded. The perf 1 command shows performance information in game for admins.

Common causes

• Entities: bases, deployables and dropped items all add up. Over weeks of a wipe, entity counts grow and the server gets slower.
• World size: bigger maps cost more RAM and CPU. Choose the size that suits your player count.
• Plugins: a badly written plugin can slow the whole server. Remove recent additions one at a time to find the culprit.
• Player count: set server.maxplayers to something your plan can handle.

What to do

1. Restart the server regularly, ideally daily. Run server.save before restarting.
2. Reduce world size on the next wipe if the server struggles.
3. Remove plugins you do not need and keep the rest updated.
4. Use plugins that clean up decayed or abandoned entities if your community allows it.
5. Check the RAM graph in the panel. If it is always near full, consider a larger plan.

Connection issues

• Cannot connect after a Rust update: the client and server versions must match. Update the server, and the framework if you use one.
• Rubber banding for one player: it is often their own connection, so ask them to test.
• Kicked with an EAC message: Rust uses Easy Anti-Cheat by default, so players need it running. Ask them to verify their game files.

If problems continue, open a ticket on our Discord and include what the Console shows.