Game Server Tick Rate Explained: 20 vs 30 vs 64 vs 128 Ticks

If you have ever rented a game server and wondered why one host charges more for “128 tick,” this is the setting behind that price difference. The tick rate controls how often the server thinks, and it decides everything from whether your shots register to how much CPU and bandwidth the machine burns. Here is what tick rate actually means, what different games use, and how to tune it without breaking anything.

What a “tick” actually is

A tick is one complete pass of the server’s simulation loop: read player inputs, run physics and AI, resolve hits, and send the resulting world state to every connected client. The tick rate is how many times per second that loop runs. A 20-tick server does 20 full simulation passes per second; a 128-tick server does 128. Everything players see — hit registration, movement, even loot timers — is sampled at this rate, which is why the number matters so much in competitive games.

Common tick rates by game

Different games make different trade-offs between simulation fidelity and hardware cost. These are the typical values you will see in 2026:

Game	Typical tick rate	Notes
Minecraft	20 TPS	Fixed; modpacks drop below 20 when the CPU falls behind
Counter-Strike 2	64 (official) / 128 (community)	128 is the competitive standard
Valorant	128	Riot runs 128 on official servers
Fortnite	30	Deliberate trade-off for large lobbies
Apex Legends	20–30	Optimized for 60-player matches
Rust	30	Server FPS is tied to tick rate
Valheim	20	Fixed by the engine
Factorio	60 UPS	The factory must grow at 60 updates per second

Some of these values are fixed by the engine and some are configurable. Always check the game’s documentation before changing the tick rate — forcing a higher rate than the engine expects can break physics and save files.

Why higher tick rates cost more CPU and bandwidth

Each tick is a full simulation pass, so doubling the tick rate from 64 to 128 roughly doubles the CPU work per second for the same player count. It also increases outgoing bandwidth, because the server sends a world-state update every tick. For a 10-slot shooter at 128 tick, plan on roughly 1.5–3 Mbps of upload just for game traffic; at 64 tick, about half that. On the CPU side, a 64-tick 10-slot server runs comfortably on one modern core, while 128 tick on a full server wants a dedicated core at 4 GHz+ that is not shared with anything else — which is why tick rate is the first thing to check when comparing hosting plans.

How to check your server’s tick rate

• Source-engine games (CS2, TF2): type stats in the server console; the Net line shows the tick rate.
• Minecraft: use /tps on Paper or Spigot servers, or install Spark for detailed tick timing.
• Rust: enable the server FPS counter in the console — Rust ties server FPS to tick rate, and a server running below 30 FPS is dropping ticks.
• Anything: watch the server console for tick warnings, or measure position-update packets per second with Wireshark.

When high tick rate matters — and when it doesn’t

Hit registration in fast shooters is the classic case: at 64 tick the server samples positions every 15.6 ms; at 128 tick, every 7.8 ms. That difference decides whether a flick shot registers on the enemy’s head or a frame too late. For survival games, MMOs, and simulation games, 20–30 ticks is standard and completely fine — nobody notices whether a loot container updates 20 or 60 times per second. Spend your hardware budget on tick rate for shooters, and on CPU and RAM for simulation-heavy games like Minecraft or Factorio.

Tuning checklist for your server

• Set the tick rate to the highest value the game officially supports — never above it.
• Give the game a dedicated core and stop the OS from scheduling other processes onto it.
• Match tick rate to player count: a 128-tick server with 24 players needs roughly double the CPU of a 64-tick one.
• Watch bandwidth: if the server’s upload pipe saturates, players see rubber-banding regardless of tick rate.
• Test ping and packet loss before blaming the tick rate — high tick rate cannot fix bad routing.

Tick rate is not ping

A common misconception: raising the tick rate lowers ping. It does not. Ping is the network round trip between player and server; tick rate is how often the server samples the world. A 128-tick server at 80 ms ping still feels worse than a 64-tick server at 20 ms. If players complain about lag, measure ping and packet loss first, then look at tick rate. For routing problems, the fix is a better server location; for the hardware itself, high tick rates under load come down to a fast single-core CPU — the kind of spec you can verify on a host that publishes real CPU models instead of vague “gaming optimized” claims.

Compare hosts that publish exact CPU clock speeds for tick-rate-sensitive servers — knowing the real specs is the only way to size correctly.