Station XX-16036 · no signal
Config Test
Offline 193.141.60.251:28027 checked 27d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,036
- top 69%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- 7d 8h
- Thu 5 Nov, 19:00 UTC FW
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The force wipe · high confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 7d 8hThu 5 Nov, 19:00 UTCFW
- 35d 8hThu 3 Dec, 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 17:40 UTC FW27d ago | M0.0■steady | 0 | – | running | 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?
Config Test uses a procedural map, which the game generates.
Which settings and rules apply on Config Test?
You will find no gather rate in the name of Config Test. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Config Test right now?
Config Test is not responding at this moment and is offline, last seen 27 days 14 hours ago.
How does Config Test rank against other Rust servers?
The last seven days of player hours place Config Test at #16,036, in the top 69% of all ranked servers.
Operator and location
How reliably does Config Test stay online?
Config Test is down at the moment; the last recorded contact was 27 days 14 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 1 October 2026.
Which region does Config Test run from?
No region is published by Config Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 193.141.60.251:28027.
Which Rust version is Config Test running?
Rust network protocol 2634 and build 166494 on Linux is what Config Test runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on Config Test?
0 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does Config Test run its wipes?
The force wipe is the only wipe Config Test takes, once a month. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. It has run its current world for 27 days 16 hours.
Lists and tags
What do the server tags on Config Test mean?
Tags published by Config Test and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): The game build is 166494; 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): Plugins or settings alter the game, so it's listed 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?
The Rust Server Trends lists that take in Config Test are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
How do you connect to Config Test?
You can connect by pressing F1 in Rust and typing client.connect 193.141.60.251:28027 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.