Offline 193.141.60.251:28022 checked 29d ago
Config Test
Connect
srv = rust.server("193.141.60.251:28023")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 29 Sep, 21:05 UTC29d ago | 0 | NaN | running | 0 |
| 1 | Mon 28 Sep, 20:47 UTC30d ago | 0 | NaN | 1 days | 0 |
| 2 | Mon 28 Sep, 13:47 UTC30d ago | 0 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 193.141.60.251:28022
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Sep 2026, 21:05 UTC
- hostname
- –
- first seen
- 28 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 159/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 184/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 71/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 15/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Quick answers
From the figures on this page.
Player counts
How does Config Test compare in the rankings?
Player hours over seven days put Config Test at #16,862, in the top 71% of the ranked set.
How full does Config Test run?
Config Test returns no live count at this refresh, having last been seen 29 days 13 hours ago.
About the server
Which Rust version is Config Test on?
Rust network protocol 2633 and build 165217 on Linux is what Config Test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Config Test, and is it online now?
Offline now for Config Test, last seen 29 days 13 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 28 September 2026.
Where does Config Test sit?
There is no region published for Config Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 193.141.60.251:28022 is its address.
Rules, settings, map
What rules and settings are recorded for Config Test?
No gather rate appears in the name: Config Test. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. Anti-cheat status: VAC on.
Which map has Config Test loaded?
A procedural map runs on Config Test, generated by the game.
Wipes and dates
When does Config Test wipe, and on what schedule?
Irregular wipe times on Config Test leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 29 days 15 hours ago.
What is wipe day on Config Test like?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 1 hours in.
Tags and filters
Which lists on Rust Data hold Config Test, and which filters?
These Rust Data lists include Config Test: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Config Test?
Read by the game's server browser, the tags Config Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into Config Test?
Enter client.connect 193.141.60.251:28022 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.