Config Test
Key statistics
the figures behind the quote- Players now
- 0/ 10 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #16,036 top 69%
- Rank · 7d ago
- #16,111 ▲75 places up
- Last wipe
- 13d ago no schedule published
- Next wipe
- 21d 22h Thu 5 Nov, 19:00 UTC FW
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 1 Oct 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes only- wipe-day peak
- 0 players, last three wipes
Coming wipes
- 21d 22hThu 5 Nov, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 17:40 UTC FW13d ago | 0 | – | running | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 127 on average | 116/300 | ▲+69+146.8% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 150/225 | ▲+69+86.0% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 90/100 | ▼−1−0.6% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average | 21/1000 | ▼−17−44.4% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 5/1000 | ▼−7−59.7% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 53/700 | ▼−1−1.4% |
Quick answers
from the figures on this pageServer Rules
What settings and rules are in place on Config Test?
No gather rate is given in the name of Config Test. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Plugin count: Carbon. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on Config Test?
The game generates the procedural map on Config Test.
Population
Where does Config Test sit in the rankings?
In the top 69% of all ranked servers, Config Test is #16,036 on player hours over the last seven days.
How many players does Config Test have?
Right now, Config Test is offline; the last sighting was 12 days 23 hours ago.
Wipe Schedule
How does Config Test handle wipe day?
The average peak across its recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
When does Config Test schedule its wipes?
Once a month, at the force wipe, Config Test wipes. On Thursday 5 November at 19:00 UTC comes the force wipe, its next wipe, and every Rust server wipes then. This world has been running for 13 days 2 hours.
Server Overview
What is the server location for Config Test?
No region is published by Config Test. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 193.141.60.251:28027.
Config Test is on which Rust version?
The build is Rust network protocol 2634 and build 166494 on Linux, running on Config Test. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of Config Test?
No response from Config Test. It was last seen 12 days 23 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. The earliest Rust Analytics saw it was 1 October 2026.
Server Tags
What is the meaning of the tags on Config Test?
These tags are published by Config Test and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166494 (Build): Game build: 166494; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Carbon provides the plugin framework. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Config Test appears in which of the lists and filters on Rust Analytics?
These Rust Analytics lists include Config Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How to Join
What is the process to join Config Test?
Type client.connect 193.141.60.251:28027 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8,^z,^y
Game
gmrust
mp10
ts8
v2634
cs166494
ptrak
$r?
Mods and access
^z
^y
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.