Counter Strike Source

How to Pad StatTrak Counters on a Private CS:GO Server

Counter Strike Source·May 20, 2026·22 min read

That fresh StatTrak weapon in your CS:GO inventory always starts the same way: zero kills. The number only ticks up when you actually drop an opponent, so building a respectable count is normally a long road. Some players go hunting for shady boosting services to fast track it, but a safer path exists. With a dedicated server, a workshop map, and a small config file, you can pile up confirmed kills without putting your account at risk.

This guide walks through the full setup.

How the StatTrak Counter Works

StatTrak is the official kill tracker baked into Counter-Strike: Global Offensive. It only moves when you eliminate a real human player. The match can be official or community hosted, with VAC enabled or off, and the count still climbs.

Bots never register on the counter. Once enough real kills are logged, the number appears on the weapon's description, in your inventory, and during matches.

Gathering What You Need

Before touching the server, three pieces of information are required:

  • A Steam Web API Key
  • A Game Server Login Token (GSLT)
  • The Workshop ID of the StatTrak boosting map

Write each value down as you generate it. They get plugged straight into the server configuration later, and a single typo will block the setup. If you already have a key and token from past CS:GO work, skip ahead to the workshop map step.

Generating the Web API Key

Open Steam's API Key page and log in with the same account you plan to use on the server.

Set the Domain field to anything reasonable. "CSGO" works.

Click Register, then copy the key Steam shows you. Keep it somewhere safe.

Creating the Login Token

Go to Steam's Game Server Management page and log in. In the App ID field, enter `730` (that is CS:GO). The Memo field takes any label you want.

Hit Create and store the Login Token alongside the API key.

Never share these values with anyone. If you suspect one has leaked, revoke it from Steam and generate a fresh one. On the hosting side, the panel keeps both private. They are mandatory for any CS:GO server to launch.

Picking the Workshop Map

The community has long settled on one specific workshop map for StatTrak boosting. It is built around quick respawns and easy kills, which is exactly the point.

Open the StatTrak Map listing on the Steam Workshop and click Subscribe so the files cache locally.

In the URL, the part after `?id=` is the workshop ID. For this map it is `345372799`. Save it alongside your other values.

Configuring the Server

Most of the configuration lives on a single panel page. You will set passwords, paste the API values, pick a game mode, and load the workshop map.

Filling in the Server Settings

From your HolyHosting control panel, open the server settings from the panel sidebar.

Choose an RCON Password. This is what you will type later to send admin commands from inside the game.

Set the Server Password as well, then tick Disable Valve Anticheat. With cheats enabled the server is no longer eligible for VAC, which is exactly what we want for this purpose.

Below those toggles, enable Allow Cheats and pick Competitive as the Game Mode.

Paste the Steam Account Token (GSLT) and the Web API Key into their respective fields.

Near the bottom, find the File ID slot and enter `345372799` so the workshop map loads on boot.

Save and head back to the main panel.

Adding the StatTrak Script

The boosting itself is driven by a small config file you upload through FTP.

Open the FTP client or file manager from your panel sidebar.

Re-enter your account password and click Login.

Browse to `csgo/cfg`.

Click New File, name it `stattrak.cfg`, and paste this block inside:

``` mp_freezetime 0; mp_maxrounds 100000; mp_round_restart_delay 0; sv_infinite_ammo 1; mp_warmuptime 3; mp_autokick 0; sv_cheats 1; weapon_accuracy_nospread "1"; weapon_debug_spread_gap "1"; weapon_recoil_cooldown "0"; weapon_recoil_decay1_exp "99999"; weapon_recoil_decay2_exp "99999"; weapon_recoil_decay2_lin "99999"; weapon_recoil_scale "0"; weapon_recoil_suppression_shots "500"; bot_kick; mp_ignore_round_win_conditions 1; mp_restartgame 1; ```

Save the file.

Restart the server from the main panel so all changes load together. Give it a couple of minutes to come back up.

Running a Boosting Session

Once the server is online, you only need one extra real player to join. A friend or a second Steam account on your end will do. Bots will not register kills on the counter, so they are not an option here.

Connect to your server and open the developer console.

Authenticate to RCON with:

``` rcon_password "Password_Here" ```

Set the time scale so rounds and respawns blow by quickly:

``` rcon host_timescale 10 ```

Then load the script:

``` rcon exec stattrak ```

Buy your StatTrak weapon and start firing. The other player respawns instantly, so kills pile up in seconds. For automatic weapons, `+attack` in the console will hold the trigger for you. Skip that for single-fire guns or you will only register one shot.

When you are done, exit the server and fully restart CS:GO before queuing for official matches. Some of the script's effects can linger on your client until the next launch.

When the Script Will Not Cooperate

The two common issues are the script failing to run and the counter freezing mid session.

If running `rcon exec stattrak` returns an error or unknown command message, the config file is probably misplaced. Reopen your FTP client, confirm `stattrak.cfg` lives inside `csgo/cfg`, and check the contents match the block above. Restart the server afterward.

Still not working? Make sure your RCON login actually went through. The command format must be exactly `rcon_password "Password_Here"`, quotes included. Successful authentication is silent, so no confirmation message is normal.

If kills stop counting mid game, restart the server. This usually happens when the map runs out of time. Running `rcon exec stattrak` again can also reset it, though the counter sometimes looks frozen in the console even when it is still tracking. A full server restart is the cleaner fix. Check your inventory or the weapon in-game to confirm the new total.

  • Spinning up a CS:GO server from scratch
  • Using workshop maps on your CS:GO server
  • Editing CS:GO server settings
  • Optimizing a CS:GO server for performance

Still have questions?

Come chat with us and we will get back to you as soon as possible!

Contact Support