Your own CS2 server on a VPS: what matters for stable play
People set up their own Counter-Strike 2 server for scrims with friends, team practice, retakes, deathmatch, surf or a small community with its own plugins. Its requirements are modest next to Rust or ARK, but it is stricter about stability: in a shooter any frame drop on the server feels like a shot that didn't register. So choosing a VPS for CS2 comes down to three things: a fast core, steady ping and a clean network.
Tickrate and the processor
In CS2 the server tickrate is fixed at 64, and shooting accuracy comes from the subtick system, which records the exact moment of a click between ticks. You can no longer set 128 tick the way you could in CS:GO, so what matters is something else: the server has to process every tick on time, even under load. A single CS2 instance lives almost entirely on one core, so clock speed is decisive. Aim for 3 GHz or more, or better, compare plans in the high-frequency VPS selection. Two cores are enough for one server with 10–12 players plus the system; for every extra instance, add another core.
Be wary of cheap plans where you share a core with neighbours. The average load there looks fine, but whenever a neighbouring server gets busy your tick runs late, and players get micro-freezes right in the middle of a firefight. If a host advertises dedicated cores, that is a real plus for CS2.
Ping and where to put the server
The table above lists servers in Russia, which suits players in Russia and the CIS best: from Moscow or Saint Petersburg a server in Moscow gives 2–10 ms, against 35–50 ms to Western Europe. If your group is in Europe, a server in Germany or the Netherlands keeps most of the continent within 10–30 ms; in North America, pick a data centre on the coast where most of you live. When your players are spread across several cities, choose the place where the main network routes meet rather than the geographic middle. For Eastern Europe and Russia that is usually Moscow, for Western Europe Frankfurt or Amsterdam. You can compare locations on the VPS in Europe page.
Being close to the players matters for more than the number on the scoreboard. Subtick records the moment of a shot precisely, but the server still has to rewind the enemy's position by the length of your ping. The higher it is, the more often players see themselves die after they have already reached cover. Jitter and packet loss matter as much as average ping: before you pay, run a long ping or mtr to the host's test IP in the evening, when the network is busiest.
If you only need the server for an evening of practice, look at hosts with hourly billing: you can create the machine before the game and delete it afterwards, keeping the server files on a snapshot or a separate disk.
Installation: SteamCMD, the token and ports
The dedicated server is installed through SteamCMD with an anonymous login using app_update 730. That is the same app ID as the game itself, so you download almost the full set of CS2 files, around 60 GB, and the size grows with updates. Plans with a 30–40 GB disk won't do, and Workshop maps and demos need extra room on top. The server runs natively on Linux, which is cheaper and lighter than Windows.
A server that appears in the public list, and that people join by more than a bare IP, needs a Game Server Login Token. You create it on Steam's game server management page using app ID 730 and pass it in the launch parameters with +sv_setsteamaccount. The token is tied to your account, and if the server breaks Valve's rules for game servers, it is the token that gets banned. The most common reason is plugins that give players skins they don't own. A server like that can lose its token, and its place in the server list along with it.
The game uses UDP port 27015, and RCON for remote management uses TCP on the same number. If you turn on GOTV to record and broadcast matches, also open UDP 27020. Give every additional server on the same machine its own port with the -port parameter.
Plugins and updates
Almost every modded server is built on Metamod:Source and CounterStrikeSharp, which lets you write plugins in C#. The admin menu, retakes, game modes and stats all run through them. This setup has one quirk worth knowing in advance: a game update overwrites the gameinfo.gi file, and after a patch Metamod stops loading until its line is added back to the file. On top of that, some plugins break after big updates until new versions come out. So it's better to update the server with a script that restores the line and restarts the server straight away, rather than by hand after players start complaining.
The server needs little memory: 4 GB on the plan is enough for one server with plugins, and for two or three servers take 8 GB. If you run several servers, a panel makes them easier to manage; see VPS for Pterodactyl.
Protection
People regularly try to take public CS2 servers down by flooding the game port. If the server is open to everyone and not just to friends with a password, look at plans with DDoS protection and ask whether it filters UDP: protection designed only for websites won't save game traffic. Payment methods differ from host to host and are listed in the payment column for each plan. For other games, see the VPS for a game server page.