Rent a CS2 server: what to check before you pay

Renting a Counter-Strike 2 server is cheap, and most of what separates a good offer from a bad one is not on the price card. What you are paying for is a share of one fast CPU core, enough memory for the mode and plugins you run, room on disk for an install of several tens of gigabytes, a location close to your players, and full access to the files so Metamod and CounterStrikeSharp can go in. You are not paying for tick rate, because there is none to sell, and you are not paying for a token, because the Game Server Login Token has to come from your own Steam account. An offer that leans on either of those is telling you how the rest of the page was written.

This post is the buyer's side of the question. The setup itself - SteamCMD, server.cfg, game modes, ports - is in Counter-Strike 2 server setup and config, and the plugin install is in Metamod and CounterStrikeSharp on CS2. Here the question is what to check before money changes hands, and when it is better to run the thing yourself.

What you are actually renting#

The CS2 dedicated server is free. It ships under the game's own Steam app id, 730, anyone can download it with SteamCMD, and Valve charges nothing per server or per player. There is no licence and no slot fee upstream of the host. Everything a host charges you for is hardware and work:

• CPU time on a machine somebody else maintains, and in CS2 that means one main thread more than anything else.
• Memory, which for CS2 is the small part of the bill.
• Disk for an install that is large by any game-server standard.
• A network address and ports that the outside world can reach, plus whatever filtering sits in front of them.
• A panel or shell access to start, stop, update and edit the server.
• Backups, support and someone else's on-call rota, which is the part you notice only when it is missing.

That list is the whole comparison. When an offer talks about something that is not on it - a premium tick rate, a bundled token, a "pro league" label - it is either decoration or a misunderstanding of how the game works. Neither is a reason to pay more.

Tick rate: the number you cannot buy#

CS:GO servers ran at 64 or 128 ticks per second, and the 128 figure became a selling point. CS2 changed the model. The server simulates at 64 tick, and player input is timestamped between ticks - the sub-tick system - so a shot is evaluated at the moment it was fired rather than at the next tick boundary. On current builds the old -tickrate launch argument does not raise that rate. Valve could change this in a future update, so if it matters to you, read what the server reports rather than what anyone, including this post, tells you.

What that means for buying:

• "128 tick CS2 server" is a label. A host advertising it has either not checked, or is counting on you not checking. It is not a reason to choose them, and charging extra for it is a red flag.
• The things tick rate used to stand in for still matter. A server that cannot finish each 15.6 ms tick on time because its CPU share is exhausted feels worse than any tick number. That is a CPU question, covered next.
• Ping is not tick rate. A smooth 64 tick server 90 ms away plays worse than the same server 20 ms away. Location is a separate decision.

What tick rate actually means goes through ticks, ping, interpolation and why people blame the wrong one. For buying a CS2 server, the summary is short: ignore any tick claim, and judge the CPU and the location instead.

CPU: single-thread speed and an enforced share#

A CS2 server does most of its work on one thread. Four slow cores do less for it than one fast one, and a plan described as "4 vCPU" can perform worse than a plan with 1.5 if the four are slices of an old, low-clocked processor shared with everybody else on the node. Reading game server CPU usage explains why a graph at 30% can still mean a server at its limit.

What to ask of an offer:

• What the CPU figure means. "1 vCPU" should be a stated share - 100% of one core, or 150% of one core - not "up to". A figure with "up to" in front of it describes the best case, which you get at 4 a.m.
• Whether the share is enforced in both directions. A hard limit means you cannot borrow a neighbour's idle time, but it also means a neighbour cannot take yours. A soft limit feels faster in a quiet hour and worse on Saturday evening. Shared CPU and noisy neighbours covers what overselling looks like from inside.
• Whether you can see it. A CPU graph drawn against the limit is how you tell a busy server from a starved one. Without it, every complaint turns into a support ticket and a guess.
• The processor generation, if the host will say. Clock speed and generation predict CS2 performance far better than core count. A host that will not name anything about the hardware is not necessarily hiding something, but you have less to go on.

What costs CPU in CS2, roughly in order: bots, which are expensive enough that a full bot roster can cost more than the humans it replaces; plugins doing work on every tick instead of on a timer; respawn-heavy modes such as deathmatch and retakes; and GOTV, mildly. A 10-player competitive match with no bots and no plugins is the lightest thing a CS2 server does.

On RE:NODE the CPU figure is a percentage of one core and a hard throttle to the share bought - Starter is 100%, the larger tiers run up to 300% - and the panel draws CPU against that limit. A server at 100% is slow, not broken, and is never suspended for it.

RAM, disk and slots#

Memory is rarely what limits a CS2 server, which is exactly why hosts like to price by it. A vanilla server sits comfortably in about 1 GB for ten players. CounterStrikeSharp brings a .NET runtime into the process, and with a handful of plugins on top the realistic floor becomes about 2 GB. Beyond that, the mode and the plugins decide more than the slot count does.

These are starting points, not guarantees. The test is the memory graph after a busy evening with every plugin loaded, plus headroom: hosts handle the memory limit differently, and on some the server is stopped and restarted the moment it reaches the line, which on a match night is the worst outcome available.

Disk is where cheap offers quietly fall over. The CS2 server install is in the region of tens of gigabytes - figures of 40 to 60 GB are normal and it grows with updates - and SteamCMD reserves the space for an update before downloading it, so a disk with too little free does not get halfway; the update simply fails and the server will not start. Demos from GOTV and workshop maps add to that. Ask how the host counts the install against your disk limit, because the answer varies, and a plan whose stated disk is smaller than the game is either counting it differently or about to stop working on the next big patch. When it does happen, game server disk space full covers the clean-up.

Slots themselves are set by you, on the launch line:

$ ./game/bin/linuxsteamrt64/cs2 -dedicated -usercon -port 27015 \    -maxplayers 12 +game_type 0 +game_mode 1 \    +sv_setsteamaccount YOUR_TOKEN +map de_inferno

Twelve rather than ten leaves room for an admin and for the GOTV bot, which takes a slot of its own when GOTV is on. The modes have their own natural sizes - competitive is 10, Wingman 4, deathmatch 16 to 24 - and a CS2 server can be set to far more than any mode makes sense with. That is the reason slot pricing is the trap covered further down.

The GSLT is yours, not the host's#

A public CS2 server needs a Game Server Login Token to register with Valve's master servers, appear in the community browser and fetch workshop content reliably. You create it at steamcommunity.com/dev/managegameservers with app id 730, on a Steam account that owns CS2, is not limited, and has a phone number registered. One token per running server.

The rule that matters for buying: the token belongs to the account that created it, and so do its bans. If a server running on a token gets that token banned, the consequences land on the Steam account behind it. That is why a host should never create one for you, and why an offer that says "GSLT included" deserves a direct question - whose account is it on, and what happens to your server if another customer on the same account gets it banned? A token on your own account, ideally a spare one that holds nothing you care about, follows you when you move hosts and cannot be taken down by somebody else's behaviour.

Without a token the server still runs, and players can still join with connect 203.0.113.10:27015 from the console. A password-protected scrim server among friends works perfectly well that way. What it will not do is list publicly. Steam game server tokens explained covers the account requirements, regeneration and the tokens that quietly expire after months unused.

On RE:NODE the token goes on the Setup tab. The server is built as soon as payment clears, and the install waits on that tab until the token is there - so the first thing to do after ordering is fetch it, not open a ticket asking why the server has not started.

Location and ping#

Counter-Strike is the game where ping is felt most directly. Peeker's advantage, trades and the sense that you died behind cover all get worse as latency rises, and no setting on the server compensates for distance. Choose the location for where your players are, not for the cheapest region on the list.

• Under about 30 ms is what competitive players expect for practice and scrims.
• 30-60 ms is fine for community and casual play.
• Past 80-100 ms a server is playable, but players will notice, and the ones furthest away will notice most.

Measure rather than guess. A host's test address or looking-glass page lets a few of your players run a ping and a traceroute in the evening, when routes are busiest. Consistency matters as much as the average: a server at 35 ms with occasional spikes to 120 plays worse than one at 45 ms that never moves. Latency, jitter and packet loss explains what to look at, and game server ping by region gives realistic figures between continents.

A long list of locations only helps if one of them is near your players, because you will run the server in one place. RE:NODE runs in one location, Germany, on hardware we run. That suits players across Europe and nearby regions; for a team in North America or Asia it is the wrong choice, and the honest advice is to pick a host near them.

Plugins, workshop maps and GOTV: the access you need#

Almost everything people want from a CS2 server beyond stock matchmaking rules - MatchZy, retakes, deathmatch with custom spawns, admin menus, surf timers - runs on Metamod:Source plus CounterStrikeSharp. SourceMod does not run on CS2. Installing that stack needs things that a locked-down host may not give you:

1. Write access to `game/csgo/`, including addons/ and the file game/csgo/gameinfo.gi, which has to be edited to add the Metamod search path. A host that exposes only a list of cvars cannot run plugins at all.
2. SFTP or a file manager that handles archives, because CounterStrikeSharp ships as a zip with its own runtime folder.
3. Control over updates. Every CS2 update rewrites gameinfo.gi and can break plugins until their authors rebuild them. You want to know whether the host auto-updates, when, and whether you can hold an update back or re-apply the Metamod line yourself afterwards.

game/csgo/  gameinfo.gi                 needs the Metamod line after every update  addons/metamod/             the loader  addons/counterstrikesharp/  runtime, plugins and configs  cfg/server.cfg              your settings

Workshop maps load by id with host_workshop_map <id> or a whole collection with host_workshop_collection <id>. They need a working token and outbound access to Steam, and they take disk. A host that does not let you set launch arguments or run console commands makes them awkward; CS2 workshop maps and collections covers map groups and rotation.

GOTV needs a second port, UDP 27020 by default, and spare upload for the spectators. If a plan comes with one port and no way to add another, GOTV does not happen. Demos recorded with tv_autorecord 1 accumulate in game/csgo/, so they also need disk and a way to download and sweep them - see CS2 GOTV and demos.

On RE:NODE every CS2 plan has two port allocations, so GOTV has a number of its own, plus SFTP and a file manager that unpacks archives in place. There is no whitelist of allowed mods; you upload Metamod, CounterStrikeSharp and plugins yourself, and the RCON password is generated per server rather than left blank.

DDoS: what a host can and cannot promise#

Counter-Strike servers attract attacks for the usual reasons: a kicked player, a rival community, a stresser service that costs less than a pizza. So every host advertises protection, and the honest version of the claim is narrower than the marketing.

Filtering upstream of a server does a good job against volumetric floods - large amounts of traffic that is plainly not game traffic - along with reflection attacks and malformed packets. It does a poor job against traffic shaped to look like real clients, such as floods of connection attempts or query packets on UDP 27015, because to a filter built for volume those look like players. DDoS attacks on game servers explained covers the categories.

What to look for in a host's claim:

• What is filtered, in plain words, rather than a terabit figure describing the provider's whole network.
• What happens when filtering is not enough. Some hosts null-route the address during a large attack to protect the rest of the network, taking your server offline until it stops. Reasonable, but worth knowing.
• No promise of zero downtime. A host that promises no downtime under any attack is selling you a sentence, not a service.

RE:NODE's wording is exactly this: upstream filtering that drops obvious volumetric floods, plus reflection and malformed traffic. Attacks that look like real players are not filtered. Your own part is a long RCON password - it travels in the clear over TCP on the game port - and not publishing the server address anywhere you do not need it. Using RCON safely is short.

Slot pricing and other price traps#

The most common trap is pricing by slot. It made some sense in the Source 1 era when the hardware was the same for everyone and slots were the only variable; for CS2 it is mostly a way to make a cheap server look expensive or an expensive one look cheap. A 10-slot competitive server and a 10-slot deathmatch server with plugins have very different costs, and a 32-slot plan that is really 1 GB and half a core will not run 32 players in any mode that matters. Translate every slot offer back into CPU share, memory and disk, and compare those.

The others, roughly in the order they cost people money:

• A tick rate premium. Covered above. Paying extra for 128 tick on CS2 buys nothing.
• "GSLT included" or "no token needed". Either the token is on the host's account, with the ban risk that implies, or the server will not list.
• A disk smaller than the install. Fine until the next large update, then a server that will not start.
• The first-month price. A discounted first month that renews at twice the rate is common. Compare the renewal price, and the price per month on a longer term if you intend to stay.
• Setup fees and paid "control panel" add-ons for things that should be standard: SFTP, backups, an RCON console.
• Backups that are extra, or that live on the same machine. A backup stored next to what it protects does not protect against losing that machine. Backups that actually restore has the questions to ask.
• Locations you will never use offered as a reason to pay more.
• No refund route. Find out how refunds work before you need one, not after.

For a sense of scale: RE:NODE's CS2 plans start at 1 GB with 100% of a core from $7 a month and run to 6 GB, with 3, 6 and 12 month terms cheaper per month. The point is not the figure but the shape - memory, CPU and price stated per tier, no slot count, no tick rate.

Renting versus running it yourself#

Running a CS2 server yourself is entirely possible and sometimes the better answer. The server is free, SteamCMD installs it with one command, and a modern desktop CPU runs a 10-player match without noticing. The question is what you give up.

At home, the obstacles are the usual ones for any game server, and hosting at home versus renting covers them in depth:

• CGNAT. Many connections no longer have a public address of their own, and port forwarding cannot fix that.
• Upload. Download speed is irrelevant; the server sends to every player, so upload is the side that counts, and it is shared with everyone else in the house.
• Your home address is the server address. Anyone who connects can see it, and an attack aimed at the server takes the household offline with it.
• Uptime. A server on the PC you play on exists only while it is switched on, and it competes with the game client for the same CPU.

For a private scrim on a LAN-quality connection among five friends, home hosting is fine. For anything public, it is the security problem that ends it, not the performance.

A rented virtual or dedicated server sits between the two. You get a public address, a datacentre network and a whole machine to yourself, and in return you do everything a panel host would: install with SteamCMD, open UDP 27015 and 27020 in the firewall, write a service unit so the server survives a reboot, script updates and the gameinfo.gi fix, set up backups and watch the disk. It makes sense when you run several servers, want root access, or have other things to run on the same machine. Choosing between a VDS and a game panel and multiple game servers on one VDS cover that route.

The panel host is the least work per server and the least control. The VDS is the most control and the most work. Neither is the wrong answer; choosing the one that matches how many hours a month you want to spend on it is the part people skip.

A checklist before you pay#

1. Location close to most of your players, confirmed with a ping and a traceroute from a few of them.
2. CPU stated as a share of a core, enforced, and visible on a graph.
3. Memory for your mode and plugins - 1 GB vanilla, 2 GB with CounterStrikeSharp, more for busy community servers.
4. Disk large enough for the install plus updates, demos and workshop maps, with a clear answer on how the install is counted.
5. Two ports if you want GOTV, and the ability to set launch arguments such as -maxplayers.
6. File access through SFTP and a file manager that can edit gameinfo.gi and unpack archives.
7. Your own token, created on your own Steam account and entered by you.
8. Backups stored off the machine, restorable by you, and an honest DDoS description.
9. The renewal price, not the first-month price, and a known refund route.

If an offer passes those nine, the remaining differences are mostly taste. How to choose game server hosting covers the parts that apply to every game.

FAQ#

How much does it cost to rent a CS2 server?

For a 10-player competitive or practice server, a small plan with about 1 GB of memory and one fast core is enough, and that sits at the cheap end of any host's list. Community servers with plugins and 16-24 players need two to four times that. The server software and the token cost nothing; you pay only for hardware and upkeep.

Can I rent a 128 tick CS2 server?

Not in any meaningful sense. CS2 runs at 64 tick with sub-tick input timing, and on current builds the CS:GO-era -tickrate argument does not change that. A host selling a 128 tick CS2 server is selling a label, so compare CPU share and location instead.

Do I need a GSLT if I rent a server?

For a public server that appears in the browser and loads workshop maps, yes, and it must come from your own Steam account. A private server where everyone joins with connect and a password works without one.

How many slots do I need for CS2?

Competitive needs 10, Wingman 4, casual 10-20 and deathmatch 16-24. Add one for the GOTV bot if GOTV is on and one or two for admins. Buy the CPU and memory those players need rather than a slot number.

Will plugins work on any rented CS2 server?

Only where you can write to game/csgo/addons and edit gameinfo.gi. Plugins run on Metamod:Source and CounterStrikeSharp, not SourceMod, and they break on CS2 updates until rebuilt, so you also need control over when the server updates.

Is it cheaper to host CS2 at home?

On paper, often - the hardware already exists. In practice CGNAT, limited upload, an exposed home address and a PC that has to stay on make it suitable for private scrims rather than a public server.