Offline 157.85.88.135:20387 checked 23h ago
Mark Test Server
Connect
srv = rust.server("157.85.88.135:20388")
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 7 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 42% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 08:58 UTC13d ago | 1 | NaN | running | 0 |
| 1 | Wed 7 Oct, 10:48 UTC22d ago | 1 | halved by day 7 | 8.9 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
3000 · seed 50000
- map
- Procedural Map
- size
- 3000
- seed
- 50000
Server
srv.info()- address
- 157.85.88.135:20387
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 09:36 UTC
- hostname
- –
- first seen
- 7 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 · 150 on average | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 187/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 83/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 256/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 350/350 |
Quick answers
From the figures on this page.
Population data
What position does Mark Test Server take in the server rankings?
Over the last seven days Mark Test Server sits at #9,435 on player hours, in the top 42% of ranked servers.
How full does Mark Test Server run?
The current row shows Mark Test Server offline; the last response was 23 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
About the server
What does performance look like on Mark Test Server?
Server fps over the last 48 hours averages 239; the floor is 233. The entity count peaked at 48,895, covering buildings, deployables and the rest of the world. Memory peaked at 3,178 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on Mark Test Server?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Mark Test Server. The protocol has to match before you can join, and Steam does the updating.
How reliable is Mark Test Server, and is it online now?
The latest sample has Mark Test Server offline, with a last sighting 23 hours ago. A restart about 32 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 162 of 168, 96%. Rust Data logged it first on 7 October 2026.
Which location does Mark Test Server run from?
There is no region published for Mark Test Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 157.85.88.135:20387.
Map and rules
Which settings and rules does Mark Test Server run?
The name Mark Test Server carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Mark Test Server selected?
The game generates the map on Mark Test Server: procedural, size 3,000, seed 50000. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does Mark Test Server wipe, and how often?
The record for Mark Test Server holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 13 days 6 hours ago.
What is wipe day on Mark Test Server like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 1 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 7.
Tags and filters
Which lists on Rust Data hold Mark Test Server, and which filters?
On Rust Data, Mark Test Server appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on Mark Test Server hold?
These tags are published by Mark Test Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to Mark Test Server?
Enter client.connect 157.85.88.135:20387 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.