Server profile
Mark Test Server
Offline, with 0 of 1 players on; ranked #9,427 of every public Rust server, the top 42%. It last wiped 13d ago.
Offline 157.85.88.135:20387 checked 1d ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 42% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
Too few wipes seen yet.
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 wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 08:58 UTC13d ago | 1 | – | running | 0 |
| Wed 7 Oct, 10:48 UTC22d ago | 1 | halved by day 7 | 8.9 days | 0 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe schedule
What should you expect on wipe day at Mark Test Server?
At their busiest, its recent wipes drew 1 players on average. The peak crowd on this wipe came 1 hours after it started. Half the peak held until the next wipe in 0% of its recent wipes. The cases that did not hold saw the crowd fall below half by day 7.
On what schedule does Mark Test Server wipe?
Its rhythm cannot be read yet: Mark Test Server has too few wipes on record. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. This world dates from 13 days 11 hours ago.
About the server
How well does Mark Test Server perform?
Average server fps over the last 48 hours was 239, with a floor of 233. At its highest the entity count reached 48,895: buildings, deployables and everything else. Memory use peaked at 3,178 MB. What players feel as lag comes from low fps and an entity count on the rise.
What Rust version is live on Mark Test Server?
Rust network protocol 2635 and build 168909 on Linux is what Mark Test Server runs. You can only join if your game is on the same protocol; Steam handles that update.
Has Mark Test Server stayed online, and is it up now?
Offline at the moment, Mark Test Server was last seen 28 hours ago. Going by the uptime figure it gives, its last restart was around 32 hours ago. The last 7 full days gave 162 of 168 hours up, or 96% of the time. The first record Rust Insights has of it is 7 October 2026.
In which location does Mark Test Server sit?
No region is published by Mark Test Server. The location shown on Rust Insights is the one a server states, not a lookup of where the machine sits. 157.85.88.135:20387 is where it answers.
Server tags
How should you read the tags listed for Mark Test Server?
The tags gmrust (Game mode): Survival as standard Rust plays; mp1 (Max players): It holds 1 slots; ts8 (Group limit): The game default applies: teams cap at 8; v2635 (Protocol): Matching versions are required, and the protocol is 2635; cs168909 (Build): Build 168909 is what it runs; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): The region code field is empty; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings alter the game, so it is filed under Modded are what Mark Test Server publishes, and the server browser in the game reads them. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
Which Rust Insights filters and lists feature Mark Test Server?
Mark Test Server appears among the following Rust Insights lists: Modded Rust servers, explained. On the server list, the filters that surface it are Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Player counts
How many players are on Mark Test Server right now?
The last time Mark Test Server was seen online was 28 hours ago, and it is offline now. The seven-day average is 0 players, and the highest point in that week was 1.
In the ranking of Rust servers, where does Mark Test Server place?
On player hours for the last seven days, Mark Test Server sits at #9,427, inside the top 42% of ranked servers.
Settings and rules
What are the settings and rules for Mark Test Server?
No gather rate appears in the name of Mark Test Server. The default of 8 players per group is what applies here. You get survival as the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. It is a Modded entry: plugins or settings modify the game. Oxide is the plugin count it runs. VAC is on: Valve's anti-cheat is active.
What is the map on Mark Test Server?
The game generates the map on Mark Test Server: procedural, size 3,000, seed 50000. Size and seed give the same map each time, so this page lets you look at it on RustMaps.
Connecting
How do you connect to Mark Test Server?
To connect, start Rust and enter client.connect 157.85.88.135:20387 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.