Tick rate is how many times per second a game server updates the match. On a 64-tick server, the server processes inputs, moves players and checks hits 64 times per second; on a 128-tick server, twice as often. Higher tick rate means the server captures what happens more precisely, which is why competitive shooters care about it. But it's one piece of the delay you feel, and usually not the biggest.
Tick rate in numbers
| Tick rate | Time between updates |
|---|---|
| 20 Hz | 50 ms |
| 30 Hz | 33.3 ms |
| 64 Hz | 15.6 ms |
| 128 Hz | 7.8 ms |
Each tick, the server collects the inputs that arrived since the last one, simulates the game and sends the new state to players. Anything that happens between two ticks waits for the next one, so the tick interval adds a small, variable delay on top of your ping.
Tick rate vs ping vs FPS
| What it is | Who controls it | |
|---|---|---|
| Tick rate | How often the server updates the game | The developer |
| Ping | Travel time between you and the server | Your connection, distance, route |
| FPS | How often your device draws a frame | Your hardware and settings |
All three affect how responsive and "fair" a shooter feels. A high tick rate can't compensate for 120 ms of ping, and 300 FPS won't help if packets are being lost. Fix what you control first: your ping, packet loss and frame rate.
Tick rates of popular games
| Game | Tick rate | Notes |
|---|---|---|
| Valorant | 128 | Riot runs 128-tick servers for all matches |
| CS2 | 64 + sub-tick | Inputs are time-stamped between ticks |
| Overwatch | 63 | Value stated by Blizzard |
| Fortnite | about 30 | From independent measurements |
| Apex Legends | 20 | Stated by Respawn |
Developers choose lower tick rates in large matches (battle royales with 60–150 players) because each tick costs server CPU and bandwidth for every player. Small 5v5 shooters can afford higher rates.
CS2's sub-tick, explained
In CS:GO, everything you did was assigned to the next tick: a shot fired just after a tick waited up to 15.6 ms on a 64-tick server. CS2 keeps 64 tick but adds sub-tick: your client records the exact moment you clicked or moved, and the server uses that timestamp when it processes the next tick. In theory, the moment of your shot no longer depends on when the tick happens. In practice, the server still updates the world at 64 Hz, so movement and what other players see still follow the tick rate. More on CS2's network settings in how to lower ping in CS2.
What tick rate means when you play
- Peeker's advantage: a player peeking a corner sees you slightly before you see them. Ping is the main cause, and the tick interval adds a little more on top.
- "I was already behind the wall": your screen showed you safe, but the server's last tick still had you exposed. Lower tick rates and higher ping make this more frequent.
- Hit registration: shots between ticks are resolved at the next tick (or by sub-tick timestamps in CS2), so very fast movements can feel less precise on low tick rates.
What you can actually do
You can't change the tick rate of official servers. You can make sure nothing else adds delay:
- Keep FPS well above the tick rate and stable, with a frame cap your PC holds.
- Lower and stabilise your ping: Ethernet, nearest server, no background traffic. Guide: how to reduce ping.
- Eliminate packet loss and jitter, which hurt more than tick rate: what is jitter.
- Fix the route if ping to the game is high on a clean wired connection. A ping booster can't change tick rate, but it can lower the network part of the delay; ExitLag alternatives lists options with free trials.
Tick rate is the server's half of responsiveness; ping, stability and FPS are yours. Get those right and the tick rate becomes the only limit left.



