Offline 157.85.85.122:27940 checked 23d ago
Test Server
Connect
srv = rust.server("157.85.85.122:27941")
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, measured since 1 Oct. 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 · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 21:59 UTC FW27d ago | 2 | NaN | 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.
display(srv.map, srv.info())Map
5000 · seed 50000
- map
- Procedural Map
- size
- 5000
- seed
- 50000
Server
srv.info()- address
- 157.85.85.122:27940
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 21:59 UTC
- hostname
- –
- first seen
- 1 Oct 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 · 151 on average | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 93/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 31/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Population
How does Test Server compare in the rankings?
Over the last seven days Test Server sits at #15,956 on player hours, in the top 71% of ranked servers.
How many players does Test Server hold at once?
Test Server returns no live count at this refresh, having last been seen 23 days 4 hours ago.
About the server
What is the Rust version on Test Server?
Rust network protocol 2634 and build 166652 on Linux is what Test Server runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Test Server, and is it up?
Test Server is offline at this refresh; the last response came 23 days 4 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 1 October 2026.
Where does Test Server sit?
No region is published by Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 157.85.85.122:27940.
Rules, settings, map
Which settings and rules does Test Server run?
You will not find a gather rate in the string Test Server. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on Test Server?
Test Server runs a procedural map of size 5,000 with seed 50000, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does Test Server wipe, and on what schedule?
Once a month Test Server wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 27 days 8 hours ago, and that is the one in play.
What is wipe day on Test Server like?
Across recent wipes the busiest point averaged 2 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does Test Server appear among Rust Data lists and filters?
These Rust Data lists include Test Server: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Test Server hold?
These tags are published by Test Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): The server lists 40 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 to join Test Server?
Enter client.connect 157.85.85.122:27940 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.