Rust PopulationField survey · Rust servers
Observing 58,911 players 11,711 servers 3,347 with someone on 176 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 16,862habitat unknownfirst seen 28 Sep 2026

Config Test

Offline 193.141.60.251:28022 checked 29d ago

moddedcarbon

Measurements

Players now
0/ 10
0% full
7-day average
0
peak –
Rank
#16,862
top 71%
Last wipe
29d ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

No hourly history yet.

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

This server has not answered a direct query in the last 48 hours.

48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k28 Sep30 Sep1 Oct3 Oct4 Oct6 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Obs. 4 · the wipe cycle

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

0.7 days
usual gap
between real wipes
0%
on rhythm
of its recent wipes
0
wipe-day peak
players, last three wipes

The first 48 hours of its last wipes

Tue 29 SepMon 28 SepMon 28 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 1 hours in.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 29 Sep, 21:05 UTC29d ago 0 – running 0
Mon 28 Sep, 20:47 UTC30d ago 0 – 1 days 0
Mon 28 Sep, 13:47 UTC30d ago 0 – 0.3 days 0

Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Field questions

Quick answers

from the figures on this page

Population

How does Config Test rank against other Rust servers?

Over the past week it ranks #16,862 for player hours, which puts Config Test in the top 71% of all ranked servers.

How busy is Config Test?

We have no live count for Config Test right now. It was last seen 29 days 12 hours ago.

Lists and tags

What do the server tags on Config Test mean?

The game's server browser reads the tags Config Test publishes: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default limit; v2633 (Protocol): To join, your game must match protocol 2633; cs165217 (Build): This server runs game build 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code is left blank; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded; ^y (Carbon): A plugin framework, Carbon, is in use. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

Which Rust Population lists and filters include Config Test?

On Rust Population, Config Test is filed under these lists: Modded Rust servers, counted. Look for it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Wipe notes

What does wipe day look like on Config Test?

The busiest point of its recent wipes averaged 0 players. The crowd on the latest wipe peaked 1 hours in.

What is the wipe schedule on Config Test?

There is no next wipe to predict: Config Test wipes at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 29 days 13 hours ago.

Settings

Which map does Config Test run?

Config Test uses a map the game generates: procedural.

What are the rules and settings on Config Test?

The name tells you nothing about gather rates: Config Test states none. Eight players per group is the default, and it applies here. This server runs survival, raid, build and gather: the standard game. Fighting and raiding between players is allowed. The server browser files it under Modded, where plugins or settings alter the game. You will find Carbon running as plugins. The anti-cheat VAC from Valve is enabled.

About the server

Which version of Rust does Config Test run?

On Linux, Config Test runs Rust network protocol 2633 and build 165217. Steam updates your game automatically, but you need the same protocol to join.

Is Config Test online, and how reliable is it?

We last saw Config Test 29 days 12 hours ago, and it is offline now. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. The first sighting by Rust Population was on 28 September 2026.

Where is Config Test located?

Nothing published by Config Test states a region. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. Connect at 193.141.60.251:28022.

How to join

How do I join Config Test?

Either enter client.connect 193.141.60.251:28022 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.

Key to its markings

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode Survival in the standard Rust style.
mp10
Max players 10 slots are available.
ts8
Group limit 8 per team is the default limit.
v2633
Protocol To join, your game must match protocol 2633.
cs165217
Build This server runs game build 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code is left blank.

Mods and access

^z
Modded The game is changed by plugins or settings, so it is listed under Modded.
^y
Carbon A plugin framework, Carbon, is in use.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.