Valve documents CS2 game-state snapshots at 64 ticks per second. There is no reliable official console switch that turns normal matchmaking into 128-tick or proves an individual server is 128-tick. The console command status can show connection/server details in some contexts, but it is not a guaranteed live tickrate meter. Use CS2 Telemetry for packet timing and network-quality indicators.
Which situation matches your problem?
Choose the closest pattern. The guide will show the most useful place to begin.
Try these steps in order
Start with reversible tests, and expand each step for more context and what its result means.
Valve’s Source 2 Telemetry HUD documentation specifies 64 ticks per second for CS2.
Open the developer console and type <code>status</code> when you are connected.
Use CS2 Game settings to display network-quality telemetry.
A local environment and a competitive server have different network conditions.
Old <code>-tickrate 128</code> instructions from CS:GO are not a verified route to changing CS2 matchmaking.
For custom-server engineering, consult the actual current server software notes.
Quick command and interpretation
This is a reference, not a guaranteed tickrate display.
General connection details — May show information depending on build and server.
Tick miss / packet timing — Shows late/missing update information rather than a 128-tick badge.
Official documented cadence — Valve’s stated Source 2 CS2 server update rhythm.
Tickrate versus subtick, in plain English
Tickrate describes how often the simulation reaches an update step. Subtick captures timing detail for relevant events between those steps. The official tick cadence therefore does not tell you everything about input timing, but that also does not make an old console tickrate flag reliable.
May show information depending on build and server.
Shows late/missing update information rather than a 128-tick badge.
Valve’s stated Source 2 CS2 server update rhythm.
Important limits and safe checks
Do not claim a server is 128 tick based solely on a client FPS graph, a launch argument or an outdated console screenshot. Separate verified documentation from server-host marketing claims.
Frequently asked questions
Focused answers for this exact CS2 problem.
What tickrate does official CS2 use?
Valve documents 64 ticks per second for CS2 server snapshots.
Does status show tickrate?
It can expose some server details, but is not a guaranteed supported tickrate meter in every CS2 build.
Is subtick the same as 128 tick?
No. Subtick timing information and server update frequency are distinct concepts.
Does -tickrate 128 change official matchmaking?
No supported client launch option forces Valve matchmaking servers into 128-tick mode.
How do I check network timing in CS2?
Use the Source 2 Telemetry HUD and focus on tick miss and jitter metrics.
Sources and verification notes
Original Walker Bex writing. Official technical guidance is separated from player reports and proposed troubleshooting tests.
References reviewed October 12, 2026
- Valve — Source 2 Telemetry HUDOfficial documentation: 64 ticks, tick misses and jitter
- Valve — Counter-Strike updatesOfficial changes in game behavior
- Steam SupportOfficial help
Walker Bex is independent of Valve. These steps were researched but not tested against a live CS2 game client; version-dependent behavior may change.