Station XX-16862 · no signal
Config Test
Offline 193.141.60.251:28022 checked 29d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,862
- top 71%
- Last wipe
- 29d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 0.7 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 29 Sep, 21:05 UTC29d ago | M0.0■steady | 0 | – | – | running | 0 |
| Mon 28 Sep, 20:47 UTC30d ago | M0.0■steady | 0 | – | 1 days | 0 | |
| Mon 28 Sep, 13:47 UTC31d ago | M0.0■steady | 0 | – | 0.3 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on Config Test?
A procedural map runs on Config Test, generated by the game.
Which settings and rules apply on Config Test?
The name of Config Test gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on Config Test right now?
A reading taken now finds Config Test offline; the most recent activity was 29 days 15 hours ago.
How does Config Test rank against other Rust servers?
On player hours for the past week, Config Test sits at #16,862, which puts it inside the top 71% of every ranked server.
Server facts
How reliably does Config Test stay online?
As recorded now, Config Test is not reachable, the last contact having been 29 days 15 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 28 September 2026 is when Rust Server Trends first recorded it.
Where in the world is Config Test hosted?
Nothing about a region comes from Config Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 193.141.60.251:28022 is the address it uses.
What build of Rust does Config Test use?
On Linux, Config Test runs Rust network protocol 2633 and build 165217. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Config Test?
On average, the busiest point of its recent wipes drew 0 players. The peak on the most recent wipe came 1 hours after the wipe.
How often does Config Test wipe, and on which days?
No next wipe can be predicted for Config Test, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 29 days 17 hours.
Tags
What do the server tags on Config Test mean?
The game's server browser reads the tags Config Test publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Config Test appear?
These Rust Server Trends lists include Config Test: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
How do you connect to Config Test?
Enter client.connect 193.141.60.251:28022 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.