Skip to content

Getting started with your Rust server

Updated June 14, 2026
Rust
Getting Started With Your Rust Server | GameServerKings KB

Getting Started With Your Rust Server

This guide walks you through the first 30 minutes with a fresh Rust server on the GSK panel: logging in, finding the server, starting it, connecting in-game, and changing the basics.

Before You Start

You need:

1. Log Into the GSK Panel

Open panel.gameserverkings.com in a browser and sign in with the email and password from your welcome message. If you have not received your credentials, check spam first, then submit a ticket.

Once you are in, your servers are listed on the dashboard. Click your Rust server to open its management page.

2. Tour of the Server Page

The left-hand sidebar has the tabs you will use most often:

  • Console is where the server output streams in real time. You can also send RCON commands from here.
  • File Manager is for editing configs, uploading plugins, and managing the server's files.
  • Schedules lets you run commands or restarts on a recurring timer (used heavily for wipes).
  • Startup is where server name, max players, seed, world size, and other launch arguments are configured.
  • Backups creates snapshots of your server volume.
  • Databases is used by plugins that need MySQL (most do not).
  • Sub-Users grants other accounts limited access to your server.
  • Settings holds your SFTP credentials and the server rename field.

3. First Boot

Hit the green Start button at the top of the Console tab. The very first boot for a Rust server takes longer than later boots because:

  1. SteamCMD downloads the Rust dedicated server files (about 11 GB at the time of writing).
  2. The server generates a procedural map from your seed and world size.

A typical fresh install on a barebones config takes 10 to 20 minutes before you see the Server startup complete message. Watch the console for that line.

If the server crashes mid-boot, check:

  • That your map size and plugin load are not too heavy for your plan (see Performance Optimization).
  • That the seed and world size in the Startup tab are valid numbers.

4. Connect In-Game

While the server is starting, grab your connection IP. It is shown at the top right of the panel page in the format 203.0.113.10:28015.

In Rust:

  1. Press F1 to open the console.
  2. Type client.connect 203.0.113.10:28015 (replace with your actual IP and port).
  3. Press Enter.

You can also add your server to your in-game favorites by joining once through F1, then clicking the star next to it in the server browser.

5. Make Yourself Admin

You cannot use admin commands until you have ownerid set. The cleanest way is from the panel Console:

Console
ownerid 76561197960287930 "YourName" "owner"
server.writecfg

Replace 76561197960287930 with your real SteamID64. You can look it up at steamid.io by pasting your Steam profile URL.

server.writecfg saves the change so it survives restarts. Without it, your admin status disappears the next time the server boots.

For moderator-level access instead of full owner:

Console
moderatorid 76561197960287930 "YourName" "moderator"
server.writecfg

6. Common First-Day Changes

Open the Startup tab. The fields most people change on day one are:

FieldWhat it does
HostnameThe server name shown in the Rust server browser
DescriptionMulti-line description shown when a player clicks your server
Max PlayersSlot count. Be conservative; 100 slots on a tiny map is misery
World SizeMap size in meters (1000 to 6000; 3500 to 4500 is typical)
SeedDetermines the procedural layout (1 to 2147483647)
RCON PasswordRequired for tools like RustAdmin to connect remotely

After changing any Startup field, restart the server for changes to apply. Some changes (world size, seed) require a full wipe to take effect, since they regenerate the map.

Made with 💜 by GameServerKings