CS2 Sub-Tick Explained

The tick rate argument dominated CS:GO server discussions for a decade. CS2 changed the underlying model, and most of the old argument no longer applies.

What a tick was

In CS:GO the server advanced the world in fixed steps — 64 or 128 of them per second — and everything that happened between two steps was rounded to the nearer one. On a 64-tick server your shot was processed as though it had been fired at the tick boundary, which is where the argument came from: at 128 the rounding error was half as large.

What sub-tick changed

CS2 timestamps your inputs. When you fire, the exact moment is sent along with the shot, and the server evaluates it at that moment rather than at the next tick. The rounding that the tick-rate debate was about is largely gone, which is why Valve ships the game this way rather than doubling the tick rate.

The world still simulates in ticks — movement, physics and grenades are not sub-tick in the same way — but shooting, the part players actually argued about, is.

What still matters

• Your ping, which sub-tick does nothing about. Distance to the server is still the single biggest factor in how the game feels.
• Packet loss, which is far more damaging than an extra few milliseconds of latency and much less often checked.
• Frame rate, because your inputs are timestamped when your client processes them.
• Server stability under load — a server dropping frames feels worse than any tick rate ever did.

So should you look for 128-tick servers?

It is no longer the marker of quality it used to be, and a community server advertising it in 2026 is mostly signalling that it copied its description from a CS:GO listing. Judge a server on whether it is stable, well moderated and close to you, which are the things that were always doing most of the work anyway.