Before anything else, a caveat about filtering by tickrate. Almost no public CS2 server tracker reports it — Valve does not expose tickrate in the A2S query the trackers rely on, so the field is simply blank nearly everywhere. That is why our directory does not print a tickrate on server cards, and why there is no live 128-tick filter on this page: a filter fed by missing data would quietly hide most of the servers you want.
If you run a 128-tick retake server, tell us when you list it and we will note it. For the format itself, start with what a retake server is.
What 128 tick actually means
Tickrate is how many times per second the server simulates the game and reconciles what every player has sent it. At 64 tick the server steps forward roughly every 15.6 milliseconds. At 128 tick it steps every 7.8. Everything that follows from that is a consequence of the smaller step: the server sees your inputs sooner, resolves who shot first with finer granularity, and sends you position updates twice as often.
What this changes in practice is small but real. Peeker's advantage shrinks slightly, because the defender's view of the attacker is less stale. Movement feels tighter, particularly counter-strafing and jiggle peeking, since the transition between moving and stopped lands closer to where you meant it. Grenade throws are more reproducible, which is why lineup guides are often recorded on 128-tick servers. None of it makes you aim better; it makes the server's version of events agree more closely with yours.
When 128 tick is worth choosing
The honest answer is: when it matches where you compete. FACEIT, ESEA and most third-party leagues run at 128, and Valve matchmaking does not. If your competitive play happens on a 128-tick platform, practising retakes at 128 means your movement and spray habits transfer without adjustment. If you play mostly Premier and Competitive in the official client, a 64-tick retake server is the more faithful rehearsal, and choosing 128 gives you muscle memory you then have to unlearn.
What 128 tick never overcomes is distance. A 128-tick server 120 ms away will feel considerably worse than a 64-tick server 25 ms away, because network latency and tickrate add together and latency is by far the larger term at that range. Filter this list to your own region before you compare anything else — the EU list and NA list do that for you.
Why not every server runs 128
- CPU cost. Doubling the tickrate roughly doubles the per-server simulation work. It is manageable at 10–12 retake slots but it demands strong single-core performance, which is the expensive part of a host.
- Bandwidth. Twice the update rate to every connected client. Not a problem for one server, noticeable for an owner running several on one uplink.
- Audience fit. Owners whose players come from Valve matchmaking sometimes deliberately stay at 64 so the practice matches.
Checking a server really is 128 tick
Treat any advertised tickrate as a claim until you check it. To verify one yourself, join the server and open the console with ~, then run:
statusand check your client-side networking with the net graph, which reports the update rate you are actually receiving:
cl_showfps 2If the server is genuinely running at 128 and your connection is healthy, your received update rate will sit near 128 rather than near 64. A server advertising 128 that delivers 64 usually means the tickrate was set in the config but the launch parameters were not.
Want the background on the format itself? Read what a retake server is, or browse the full directory. Running a 128-tick server that is not here? List it for free.