CS2 Sub-Tick: What Valve Actually Said

Open any CS2 discussion about a duel someone thinks they should have won and sub-tick will be blamed inside three replies. It is the most talked about and least read feature in the game.

Valve wrote about four sentences on it. That is the entire official account. Everything else you have read, including the millisecond figures and the confident claims about hit registration, was written by someone who was also guessing.

Here is what sub-tick actually is, what Valve does and does not claim, and the arithmetic that shows why it had to exist.

What a tick is, in milliseconds

A Counter-Strike server does not watch the game continuously. It wakes up, looks at the world, works out what happened, and goes back to sleep. Each of those wake ups is a tick.

At 64 tick the server wakes up 64 times a second, which is one update every 15.625 milliseconds. At 128 tick it is 7.81 milliseconds. That is simply 1000 divided by the tick rate, and it is the only number in this whole topic that is not in dispute.

In the old model, anything you did between two ticks did not exist until the next one arrived. You fired, and the server filed the shot at the next wake up, with the world in the state it was in at that moment rather than the state you were looking at.

Pull the trigger 24.3 milliseconds into the round on a 64 tick server and the old model records the shot at 31.25, which is the next tick boundary. Your click was 6.95 milliseconds late by the time it counted, and the enemy had kept moving for all of it.

Sub-tick is the fix for exactly that. In Valve's own words, servers now know the exact instant that motion starts, a shot is fired, or a nade is thrown. The shot is stamped at 24.3, not at 31.25.

Your monitor was already faster than the server

This is the part that makes the problem obvious, and it is pure arithmetic.

A 144 Hz monitor draws a new frame every 6.94 milliseconds. A 64 tick server updates every 15.625. So you were being shown more than two frames of new information for every single server evaluation. On a 240 Hz monitor it is nearly four frames. On 360 Hz it is over five.

Think about what that means. Your screen was telling you the truth at a resolution the server could not act on. You were aiming at a position that existed between two server wake ups, and the server had no way to represent the moment you clicked.

That gap is why the old game felt inconsistent at high refresh rates specifically. The faster your monitor, the more of your inputs landed in the dead space between ticks.

If you have never checked that your monitor is actually running at its rated refresh rate rather than quietly sitting at 60, the refresh rate guide covers how to confirm it in thirty seconds. It is the single most common silent settings mistake in CS2.

What Valve actually claims, and what it does not

The left column is Valve's own wording from the Counter-Strike 2 page. The right column matters just as much.

Valve has never published a tick rate for official CS2 servers. Not in the announcement, not since. The number you see quoted everywhere is community reporting, not a stated figure.

Valve gives no millisecond improvement figure. Any article telling you sub-tick saves you a specific number of milliseconds invented it.

Valve says nothing about peeker's advantage. Sub-tick is described as timing, not as a fix for the geometry of who sees whom first. Those are different problems, and peeker's advantage is covered properly in its own guide.

Valve says nothing about hit registration accuracy. The claim is about when events are recorded, not about whether a bullet that visually connected will be counted.

So when someone tells you a duel was lost to sub-tick, ask which of those four things they mean. In most cases the answer is none of them.

What sub-tick does not fix

Three things get blamed on it constantly and are not it.

Your ping. Sub-tick times events precisely. It does not make the trip from your machine to the server any shorter. A 60 ms connection is still a 60 ms connection, and no amount of timing precision closes that.

Your frame rate. If your game is running at 80 frames, you are seeing a new picture every 12.5 milliseconds no matter how precisely the server timestamps things. You cannot click on information you have not been shown yet.

Your crosshair placement. This is the honest one. The overwhelming majority of duels described as a sub-tick problem were duels where the crosshair started at chest height, or on the wrong side of the door. That is a crosshair placement problem with a known fix, and it costs far more rounds than any netcode question.

How to tell the difference yourself

You do not have to take anyone's word on this, including mine. Watch your own demo.

Pause the frame before the duel resolves and look at two things. Where was your crosshair when the enemy became visible, and were you moving when you fired. If the crosshair was off the angle, or you were still carrying momentum, the netcode never entered into it.

Do that on five duels you were sure you won and the pattern usually resolves itself in about ten minutes. The demo review checklist walks through exactly what to pause on and in what order.

And before you change a single setting because of something you read about sub-tick, make sure the settings you already have are sane. The settings that actually matter is a short list, and almost nothing on it is network related.

Where to go next

The reason this topic swallows so much attention is that it feels like an explanation you cannot be blamed for. It is not. Sub-tick made the timing of your inputs exact, which means your inputs are now the variable.

So the useful work is upstream of the server. Build a crosshair you can actually see against a smoke in the CS2 Crosshair Generator, then make sure the sensitivity you are aiming with is one your mousepad can physically support, with the eDPI Calculator. Both take under a minute.

If you want to see what the players at the top are doing with that responsiveness, the CS2 Pro Positions tool shows where every player on an HLTV top 50 team stands round by round, and which positions actually win the first duel. And to compare your own record against a specific opponent rather than against an average, the FACEIT Head-to-Head tool puts both histories side by side.

For the number that tells you whether your aim is genuinely improving, what counts as a good ADR explains why headshot rate moves between ranks and ADR barely does.