What Is Server Tick Rate and Why Does It Matter?

Hertz units measure how often a game server refreshes its match simulation each second, producing dozens or hundreds of discrete snapshots during play. A 64-tick server snapshots player positions, projectile paths, and hitboxes every 15.6 milliseconds, while a 128-tick server does the same roughly every 7.8 milliseconds. Those intervals quietly decide whether a headshot connects through a narrow gap or vanishes into the void.

This guide covers the fundamentals of server tick rate, from hertz measurements to the real-world differences between 64-tick and 128-tick matches, and helps competitive FPS players understand why their shots sometimes fail to register.

Tick Rate Is the Server’s Heartbeat, Measured in Hertz

Every multiplayer match runs on a loop driven by a clock that lives entirely on the server, never on your machine. Each tick, the server collects input from every connected client, advances the simulation one step, and pushes the updated world state back out to players.

What One Tick Actually Represents

One tick is a single complete update pass: positions, velocities, weapon states, health, and physics all reconcile at the same instant. At 64 Hz, that pass happens 64 times each second; at 128 Hz, it happens 128 times. The interval between ticks drops from 15.6 ms to 7.8 ms, and that thinner slice of time is where competitive edges live or die.

Server Tick Rate vs Client Frame Rate

Your monitor might refresh at 240 Hz or higher, and your GPU may push hundreds of frames per second, yet none of that changes the server’s clock. A 128-tick server sends 128 updates per second, and your client interpolates the gaps with extra rendered frames so movement looks fluid between packets. The server is the source of truth; your hardware is the display layer.

Tick Rate	Updates per Second	Interval Between Ticks
32 Hz	32	31.25 ms
64 Hz	64	15.6 ms
128 Hz	128	7.8 ms
240 Hz	240	4.2 ms

Higher numbers mean a denser stream of authoritative data, but the cost lives on the server side, and that cost scales fast.

How Tick Rate Shapes Hit Registration and Player Movement

Hit registration, the moment the server confirms a shot landed, depends on comparing where the shooter aimed against where the target was during the tick the shot was processed. A denser tick stream shrinks the gap between the target’s actual position and the position the server has on file.

Lag Compensation and the Server’s Rewind

To keep hits feeling fair across laggy connections, modern shooters briefly rewind the match clock on the server so shots register against what the attacker actually saw. A 64-tick server rewinds in 15.6 ms steps; a 128-tick server rewinds in 7.8 ms steps. Smaller steps produce finer judgment, and finer judgment means fewer shots that should have hit slip through the gaps between snapshots.

Peeker’s Advantage and Why It Happens

When a player swings around a corner, the aggressor sees the defender before the defender’s new position reaches the server. On lower tick rates, that visibility window stretches longer because updates arrive further apart. At 128 Hz, the aggressor’s visible advantage shrinks by roughly half compared to 64 Hz, which is one reason professional players notice the difference in tight duels.

That advantage shows up in moments you already recognize: a spray that lands five bullets but registers three, a long-range strafe that feels rubbery, a trade kill that fails to credit because the second shooter died one tick too early.

Those misfires trace directly to the sampling interval, so a closer look at 64-tick versus 128-tick servers reveals where the differences actually surface.

Comparing 64-Tick and 128-Tick in Practice

At the center of competitive shooter discourse sits a heated debate over whether 64 or 128 server updates per second delivers a meaningfully better experience. Most official matchmaking in Counter-Strike 2 runs at 64 Hz, while Valorant uses 128 Hz on Riot’s servers by default. Third-party services like Faceit offer 128-tick CS2 matches, and many community servers let you configure either rate.

Where the Difference Actually Shows Up

Casual players often cannot tell the two apart without a side-by-side test, and that’s the honest truth. Pro players, high-rank grinders, and anyone logging hundreds of matches a month tend to report more consistent spray control, fewer phantom misses, and tighter peek duels at 128 Hz. The gap shows up most in long-range engagements, coordinated utility usage, and tightly timed shoulder peeks where a few milliseconds decide the round.

Game-by-Game Defaults

Valorant runs 128-tick servers as a baseline, a deliberate choice by Riot Games. Counter-Strike 2 still uses 64 Hz on official matchmaking, though Valve’s Sub-tick system processes input timestamps rather than relying on a fixed clock. Older Source Engine titles like CS:GO and many Battlefield matches historically ran at 32-tick or 64-tick, and the modding scene often pushed 128-tick for competitive leagues.

Title	Default Official Tick	Tick Rate on Third-Party
Counter-Strike 2	64 Hz (Sub-tick input)	128 Hz on Faceit and select leagues
Valorant	128 Hz	N/A (closed ecosystem)
Overwatch 2	63 Hz (close to 64)	Limited third-party competitive
Battlefield 2042	60 Hz (console), 30 Hz on some platforms	Custom server configs vary

Notice that the defaults reflect each developer’s balancing act between competitive integrity and the cost of running millions of matches simultaneously.

Tick Rate Is Not the Same as Ping or Latency

Tick rate and latency get tangled together in casual conversation, yet they measure completely different things. Tick rate sets how often the server snapshots the world, while latency, usually reported as ping in milliseconds, sets how long a data packet takes to travel from your machine to the server and back as round trip time (RTT).

Why High Tick Rate Cannot Fix Bad Ping

A 128-tick server paired with 150 ms of ping will feel worse than a 64-tick server with 20 ms of ping. The server may update twice as often, but each update is already stale by the time it reaches you, and your inputs arrive late. Hit registration depends on both density and freshness, and freshness lives in your network connection, not in the server’s clock.

The Three Numbers That Actually Matter

Three measurements shape how a match feels: tick rate sets update density, latency sets how stale each update is by the time it reaches you, and your client frame rate renders the result. A stable 20 ms connection on a 64-tick server often feels smoother than a jittery 80 ms connection on a 128-tick server. The green connection bar in your HUD measures RTT, not tick rate, and a green bar does not guarantee responsive hit registration when packet loss is high.

Yet identical latency can mask wildly different server behavior, which is why the cost curve behind high tick rates deserves its own examination.

The Cost and Engineering Tradeoffs Behind Higher Tick Rates

Doubling the tick rate does not double the server’s work cleanly. Each tick consumes CPU cycles to process inputs, memory allocations to track state, and outbound bandwidth to push updates to every connected client. Scale that across thousands of matches running in parallel, and the infrastructure bill grows fast.

Why Developers Default to 64-Tick

Valve, Riot Games, and other publishers run matchmaking at a frequency that balances fairness with operational cost. A 64-tick default lets them serve millions of concurrent matches on a fixed hardware budget. A 128-tick default would roughly double CPU and bandwidth costs per match, and those costs eventually show up in subscription prices, premium matchmaking fees, or community server rentals.

Sub-Tick and Variable-Rate Architectures

Some modern titles experiment with sub-tick input, a system that timestamps player actions precisely rather than snapping to a fixed clock. Counter-Strike 2’s Sub-tick model aims to deliver 128-tick responsiveness with less server overhead by sending updates only when meaningful state changes. Variable tick rate is another approach: the netcode runs fast during firefights and slows during downtime. Both are engineering responses to the cost curve that fixed high tick rates create.

“Tip: When a match feels off, check your ping graph before blaming the server. Stable 40 ms on 64-tick beats spiking 90 ms on 128-tick almost every time, especially when packet loss is above 1%.

Choosing Servers and Settings That Match Your Playstyle

Tier lists and defaults matter less than your own habits. A casual weekend player gains almost nothing from chasing 128-tick matchmaking. A ranked grinder pushing Immortal or FACEIT level 10 notices the difference every night.

A Layered Decision Path

Start with your connection. A wired ethernet setup, a router close to your machine, and a regional server with under 30 ms ping form the foundation. Once that foundation is stable, look at tick rate as the next lever. For CS2, that means selecting Faceit or ESEA for competitive practice, or finding a well-configured community server. For Valorant, the choice is already made for you. For Overwatch 2 and Battlefield, the defaults are usually the only realistic option.

Actions That Move the Needle

• ▸Lock down a stable connection: Use ethernet, pick the closest regional server, and avoid Wi-Fi during ranked play.
• ▸Choose 128-tick when available: Select Faceit, ESEA, or any verified 128 Hz service for serious CS2 practice.
• ▸Watch your replay tool: Many shooter replay viewers show whether shots registered, and the pattern over time reveals whether tick rate is hurting you.
• ▸Match settings to your rank: Lower ranks gain more from crosshair placement and utility timing than from tick upgrades.
• ▸Test before committing: Spend 20 matches on 128-tick before deciding. The difference is subtle until it isn’t.

The honest hierarchy puts skill first, latency second, hardware third, and tick rate fourth. Tick rate matters, but it sits behind the fundamentals that actually decide gunfights.

With that hierarchy in mind, the practical question becomes how to pick servers and settings that actually fit the way you play.

Bottom Line

Tick rate is the density of truth a server delivers each second, and denser truth means fairer fights. Higher tick rates sharpen hit registration, shrink peeker’s advantage, and smooth out the moments where a 15.6 ms gap swallows a kill. The catch is cost, both in infrastructure and in your time spent chasing marginal gains. Lock down your connection first, choose 128-tick servers when the stakes warrant it, and let skill do the rest.

FAQ