Rust Server Tickrate: How to Configure and Optimize in 2026
Tickrate controls how many times per second your Rust server processes the game world. The default is 30. Higher tickrate means smoother player movement and combat. Lower tickrate reduces CPU load but makes gameplay less responsive.
What is Tickrate in Rust?
Every tick, the server processes player inputs, updates entity positions, runs decay timers, processes AI, and handles network sync. At tickrate 30, this happens 30 times per second. Each tick has a budget of 33.3ms. If a tick takes longer, players experience rubber-banding and desync.
How to Change Tickrate
Startup command:
./RustDedicated -batchmode +server.port 28015 +server.tickrate 30
server.cfg:
server.tickrate 30
Via RCON (not recommended for production):
server.tickrate 30
server.save
Changing tickrate during gameplay causes a noticeable jolt for connected players. Restart the server when changing it.
Tickrate Values and Their Impact
| Tickrate | Tick budget | CPU load | Feel | |---|---|---|---| | 10 | 100ms | Very low | Sluggish, noticeable desync | | 15 | 66.7ms | Low | Below average | | 30 | 33.3ms | Medium | Default, standard gameplay | | 60 | 16.7ms | High | Smoother PvP | | 100 | 10ms | Very high | Competitive, demanding |
Tickrate 30 (Default)
What Facepunch designed the game for. Most servers run at 30. It balances server load against responsiveness.
Tickrate 60
PvP feels noticeably smoother. Hit registration improves. The tradeoff: your server CPU works twice as hard. A server handling 150 players at 30 handles only 60-80 at tickrate 60 with the same hardware.
Tickrate 10-15
Some heavily modded PvE servers lower tickrate to reduce CPU usage. Movement feels delayed. Only for PvE or RP servers where performance ceiling matters more than responsiveness.
Hardware Requirements
| Tickrate | Recommended CPU | RAM | |---|---|---| | 30 | Modern quad-core | 8 GB | | 60 | Ryzen 7/9 or equivalent | 12 GB | | 100 | Ryzen 9 7950X3D or better | 16 GB |
Rust's main game loop is single-threaded. Clock speed and IPC (instructions per cycle) matter more than core count.
Monitoring Performance
Use RCON: perf 1 shows time taken per tick. If the average exceeds your tick budget (33.3ms at tickrate 30), your server is lagging.
Entity count and tickrate
Every entity (sleeping bag, furnace, door, dropped item) adds processing time per tick. Day 3 of a wipe with 100,000+ entities pushes tick times up.
Solutions:
- Set entity limits via
server.maxunloadedentities - Schedule aggressive upkeep decay to remove abandoned bases
- Use a smaller map (3,000-3,500 instead of 4,500)
- Clear dropped items regularly
The Optimal Setting
For most community servers: tickrate 30. Default, expected by players, and balanced.
For competitive or PvP-focused servers on good hardware: tickrate 60. Players notice the improvement in gunfights.
Host a Rust Server
Space-Node Rust servers run on AMD Ryzen 9 hardware with NVMe SSDs. Single-thread performance keeps your tickrate stable even on day 3 of a busy wipe. Servers in the Netherlands and Canada with DDoS protection included.
